Skip to main content
All mutating and most read endpoints require an authenticated user context (OIDC access token), not device MQTT credentials.

​
Headers

Some project-scoped routes also expect the project ID in the URL path (/projects/{project_id}/…).

​
Obtaining a token

For local development with AUTH_BYPASS=true on apis, any bearer token works together with X-Test-User-ID (e2e harness only).

​
Playground notes

The interactive API playground on this site sends requests from your browser. You must paste a valid Bearer token and ORG-ID into the playground auth fields.
Do not paste production tokens into shared machines or screenshots. Prefer short-lived staging tokens for playground testing.

​
Device and edge traffic

Devices authenticate to MQTT with mTLS or username/password — not this HTTP Bearer flow. Edge SQLite sync governance uses the same user API (/projects/{id}/edge/…) documented in the edge sync API summary.