Management keys and bots
Pick the right key
Create account-level keys in API Keys. An Elite Key requires a plan with Elite API access. A Bot Key requires a plan with a supported bot. Keys can have expiry dates, scopes and source restrictions. Keep them on your server and revoke them if exposed.
Send the key as Authorization: Bearer YOUR_MANAGEMENT_KEY. An AppKey or SDK session token cannot replace it.
Permissions
Permissions use resource.action, for example licenses.create or applications.info. The API checks the account’s active plan and the required permission on every request. A key with list access cannot silently gain create, ban or delete access.
Read records
Use GET /management/v1/licenses?appId=APP_ID&limit=50&offset=0. Read data and nextOffset; when nextOffset is null there is no next page. Results are scoped to the key’s owner and omit secret-like fields.
Change records
Use POST on the resource path with an action. For example:
For licenses, omitting values.name generates a key. The default is four groups of four characters. keyGroups and keyLength each accept 3 to 5. subscription is the app plan name, not the developer’s AuthlyX billing plan.
For edit/delete, include the record ID and its app ID. The API reference lists supported actions for each resource. Changes are audited. Browser origin checks restrict requests but do not prove a caller’s identity.
Bot commands
POST /bots/v1/commands accepts a Bot Key. It supports apps, status, license, pause, resume, ban and unban. Permissions still apply. Hosted Discord and Telegram callbacks validate provider signatures/secrets and are not generic customer API endpoints.
Current scope
These public management endpoints cover applications, users, licenses, devices, plans and cloud variables. They do not expose the private admin dashboard or every internal settings mutation. Do not build integrations against dashboard cookie endpoints.

