Brellium Public API

Org-scoped public REST API over Brellium's documents, audits, coding evaluations, users, and question sets. OAuth2 client-credentials auth; cursor pagination; snake_case JSON.

Consistency: Reads are eventually consistent: list/get responses are served from a replicated read store that typically lags writes by a few seconds. Responses returned by create/update/confirm calls always reflect the write you just made — treat those response bodies as the source of truth immediately after writing, rather than re-fetching.

Credential handling: Client credentials are for servers only — never embed client_id/client_secret (or access tokens) in browser or mobile code. Mint tokens from your backend and keep them there.