Documentation
Authentication
Every request to the Klang API must carry your API key as an HTTP bearer token.
Header format
Authorization: Bearer sk_…
If the key is missing or wrong you'll get a 401 with {"error": {"type": "auth", "message": "…"}}.
Where keys come from
Keys are managed in Settings → Developers → API keys in the Klang app. Each key is bound to a single workspace and the user who created it.
Identify which workspace a key resolves to with GET /api/v1/me. It returns the user email and workspace name the key is bound to.
Keep keys server-side
Keys grant the same access your application has. Never embed them in client-side JavaScript, mobile apps, or any environment a user can read. Use environment variables on your server and rotate keys if you suspect they've leaked.