API access belongs to developer accounts.
Azari Developer uses its own account, password, OTP and session. A normal Azari Select member account does not sign you in here, and a developer account does not sign you in to the member app. After verification, developers can register applications, receive scoped sandbox credentials and request reviewed live access.
Separate developer authority
Member authentication establishes identity. Developer-account enrolment separately establishes API authority.
One-time secret display
Credential secrets are displayed at issuance and are not recoverable later. Rotation issues a replacement.
Reviewed production access
Live access requires the applicable KYC/KYB state, business context and Azari Select approval.
Documentation is separate
docs.azariselect.com is the API documentation and reference surface. It does not create accounts or grant keys.
Developer console
Sign in with your Azari Developer account, or create one here. Developer authentication is isolated from Azari Select member authentication; credentials and sessions are never shared between the two products.
Register an application
Applications and credentials are owned by your Developer Account, not by the ordinary member product.
Your applications
Access lifecycle
Authenticate
Sign in and complete the account verification challenge.
Activate Developer Account
Accept the developer terms. Until this relationship is active, application and key endpoints deny access.
Register and test
Create an application and copy the scoped sandbox secret when it is issued. Build against the documented external API.
Request live access
Submit the production request. ARRK reviews the application and may approve, decline, suspend or revoke access.