Documentation
Aroli documentation
Everything you need to add accounts, license keys, device limits and subscriptions to desktop and native software.
Core concepts
- Organization - your company account in the dashboard. Team members, billing and plan limits live here.
- Application - one product you ship. Each has a public app ID (
app_…), its own Ed25519 signing keys, device-binding settings, users, licenses and variables. - End user - an account registered inside one application, signing in from your software.
- License key - a code that grants time on a product (an entitlement) when redeemed, or validates on its own in license-only mode.
- Entitlement - whether a user currently has access to a product (for example
pro) and until when.
Two APIs
The client API (/api/v1/client/…) is called by the software you ship. It identifies your app with the public X-Aroli-App header and signs every response. The management API (/api/v1/management/…) is called by your servers with a secret key and can do anything the dashboard can.
Never ship secret keys
Secret keys (ak_dev_…, ak_live_…) must stay on your server. Anything inside a binary you distribute should be treated as public.
A machine-readable OpenAPI description is available at /api/v1/openapi.json.