Authentication
Talqen uses application-scoped API keys. Send them as Bearer tokens from server environments only.
Authorization header
Required headerhttp
Authorization: Bearer <TALQEN_API_KEY>Credential prefixes
- Test:
talqen_test_→https://api-staging.talqen.net - Live:
talqen_live_→https://api.talqen.net
Test and live credentials are separate. A test key is rejected on the production gateway, and a live key is rejected on staging.
Application and workspace scope
Workspace membership for integrator routes comes from the approved API credential. You do not authorize access with a workspace header. Allowed Roblox universe IDs are stored on the developer application; an empty list denies all universes.
Scopes
| Scope | Usage |
|---|---|
| activity:write | Shift start, heartbeat, and stop |
| activity:read | Active shifts, summaries, and leaderboard |
| staff:read | GET /v1/staff/me |
| applications:read | Catalogued; no public integrator route yet |
| permissions:check | Catalogued; no public integrator route yet |
| events:write | Catalogued; no public integrator route yet |
| activity:manage | Catalogued; no public integrator route yet |