Authorization: Bearer or x-api-token for authentication — see Authentication for the full matrix.
Available APIs
Integration API
User-scoped operations — challenges, rewards, achievements, and profile data for logged-in members
Admin API
Administrative operations for platform configuration, content management, and RBAC
Analytics API
Reporting endpoints for engagement metrics, leaderboards, and challenge performance
Base URL
Every request is scoped to your organisation’s subdomain:{your-subdomain}is assigned when your organisation is provisioned (e.g.acme-corp). White-label custom domains are configurable via the Admin API’s/domainsendpoints — see Custom Domains.{api-type}is one ofintegration,admin, oranalytics.- All requests must hit the subdomain that matches the token — cross-tenant token reuse is rejected at the auth middleware.
Making Your First Request
The example below usesAuthorization: Bearer (recommended for new integrations). The legacy x-api-token header is also accepted everywhere — the runtime strips the Bearer prefix automatically if present.
Next Steps
Authentication
Bearer tokens, legacy
x-api-token, per-API auth matrix, and best practicesErrors
The tRPC error envelope and common status codes
Pagination
The
limit / skip contract and totalCount + edges response shapeCustom Domains
Domain patterns, white-label URLs, and how tokens are scoped to hosts
Webhooks
Outbound events, signing, retries, and idempotency
Internationalization
The
x-language header and translated response bodies
