API reference
Problem types
Every error a Kleora API returns is an RFC 9457 problem document, sent as application/problem+json. Its type is the address of one of these pages, and the slug at the end of it is the part to branch on: it is stable, where title and detail are prose and may change.
Besides type, title and status, a document may carry detail (this occurrence, in English), instance (the request path) and request_id, which matches the response’s X-Request-Id — quote it when you ask us about a request. The hosted pages’ API and the account API add code, the slug in snake_case.
400Bad Request
401Unauthorized
402Payment Required
403Forbidden
404Not Found
409Conflict
- Account limit reached
- Workspace belongs to an account
- Already a member
- API key cannot be rotated
- Default client
- Client has no secret
- Conflict
- Default workspace
- Address already taken
- Idempotent request in progress
- Invitation already open
- Last way to sign in
- Last owner
- Second factor already enrolled
- Not a sandbox
- Authenticator already registered
- Permission already exists
- Platform protected
- Provider identity already linked
- Identity provider in use
- Role slug taken
- Setting already defined
- Setting type conflict
- Membership fixed in single mode
- Slug reserved
- Slug taken
- Reserved management permission
- Platform-created role
- Membership backfill still running
- Environment in single mode
- Cannot switch to single mode
- User erased
- Webhook endpoint disabled