All mutating and most read endpoints require an authenticated user context (OIDC access token), not device MQTT credentials.Documentation Index
Fetch the complete documentation index at: https://docs.ilyama.golain.io/llms.txt
Use this file to discover all available pages before exploring further.
Headers
| Header | Required | Description |
|---|---|---|
Authorization | Yes | Bearer <access_token> from Zitadel OIDC |
ORG-ID | Yes | UUID of the active organization |
Idempotency-Key | Mutations | Unique key per logical write; forwarded to domain workers |
/projects/{project_id}/…).
Obtaining a token
| Client | Method |
|---|---|
Web console (pw) | Zitadel authorization code flow in browser |
platform-tui | OAuth device authorization — login guide |
golain-cli | OAuth browser flow |
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.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.