Skip to navigation

Connect your app

Copy your application details

Use the details of the same application that contains your licenses and users. Keep the existing owner ID unchanged when moving an account.

Initialize

Send POST /api/v2/init with the four connection fields:

{
"owner_id": "459010927960",
"app_name": "MyApp",
"version": "1.0.0",
"secret": "YOUR_APPLICATION_SECRET"
}

The secret above is a placeholder: paste your own application’s secret when testing privately. Never put an Elite Key here.

Initialization returns the legacy session information. Keep that session in memory and use it for the next request. Initialization alone does not sign in a customer.

Choose how the customer signs in

AccessRouteCredentials
Username/api/v2/loginUsername, password and system ID
License/api/v2/licensesLicense key and system ID
Device/api/v2/device-authDevice type and device ID

Use the API Reference for the complete request fields, including session_id. Do not add V3 challenge headers to these requests.

Keep checking access

Call /api/v2/validate-session while protected features are in use. A successful sign-in is not a permanent approval. A developer can later pause, ban or expire access.

If access is rejected, stop protected operations and let the customer sign in again. A connection failure is different from a server response that says the license is banned.