Skip to main content
Before writing code you need three things: a staging login, an application of the right type, and that application activated by Fluz if it will act for anyone other than you. Read How accounts work first if you haven’t. It explains the terms used here.
Everything starts in staging. Sign up and create applications at uni.staging.fluzapp.com, not at fluz.app. Anything created on fluz.app is live.
1

Sign up in staging

Go to uni.staging.fluzapp.com and sign up. This creates a staging user with a personal account.Already have a live Fluz login? Staging is a separate system: sign up there too. You can also open it from the live dashboard under Resources → Open Staging.
2

Pick the application type

Open uni.staging.fluzapp.com/for-developers.
  • Acting only on your own account? Click Create new app.
  • Acting for other users (registering customers, KYC/KYB, issuing cards for them)? Go to Templates and choose OAuth Integration.
Platforms need OAuth Integration. An app made with Create new app can only call the API as its developer, and can’t be converted later.
3

Ask Fluz to activate the application

New applications are not active. They work only on the developer’s own account until Fluz moves them to ACTIVE. Send the application name or ID to your Fluz contact, together with any restricted capabilities you need: registerUser, VERIFY_KYC, or restricting the app to business accounts.Until the app is activated, platform calls fail with AUTH-0030 … current status: PERSONAL.
4

Copy your credentials

Open the application to find its API Key, User ID and Account ID. The Account ID is the account this application’s own tokens act as. Continue to API credentials.

​
Is my company’s staging account a business?

If Fluz set up a staging business account for your company during onboarding, that account already exists alongside your personal one. Use Get Accounts to find its accountId, and mint tokens against it when you need a BUSINESS token.

​
Setting up a team of developers

To give each developer an isolated sandbox, so tests don’t share data:
  1. Each developer signs up in staging with their own email and phone. Each gets their own personal account.
  2. Each developer creates their own OAuth Integration application and sends it to Fluz to activate.
  3. Each developer creates their own test business if they need a BUSINESS account. Use registerBusiness with the approved test tax ID from KYB Testing.
Prefer one shared login? A single account can hold several applications, each with its own key. You can also add teammates as authorized users. Both share one ledger, so tests will see each other’s data.

​
Next steps

API credentials

Mint a token for the right account.

Fund your staging wallet

Put test money in before you issue cards.