Application types
What an application can do is decided when you create it:
An application can’t be switched from one type to the other. If you need OAuth, create a new application from the OAuth Integration template. See How accounts work.
Application status
Fluz moves applications to
ACTIVE; it isn’t self-serve. Send the application name or ID to your Fluz contact. Until then, calls that act for other users fail with AUTH-0030 … current status: PERSONAL.
Fields on an application
Each application has the following fields:- Display Name — must be unique; shown when you request access from a user.
- Developer Contact — the contact information for this application. Recommended for any publicly available application.
- App Logo — an image file, shown in the app marketplace.
- App Sub Title — a short one-line explanation of the application.
- App Description — the overview description of the application.
- App Visibility — controls whether the app is available only on your Fluz account or to the wider Fluz network.
API keys
Each application has an API key, User ID, and Account ID. The Account ID is the account this application’s own tokens act as. Staging and live are separate systems, so an application and its key exist in only one environment.Staging API keys
Log in to uni.staging.fluzapp.com/for-developers and open the application. From the live dashboard, you can reach staging under Resources → Open Staging. Staging is a separate login, so if you haven’t signed up there yet, sign up first.Production API keys
Log in to fluz.app/for-developers and open the application. A production application must be created, and activated by Fluz, separately from its staging counterpart.Next steps
API credentials
Use the key to mint an access token.
Application scopes
Choose what your application may request.