API and single sign-on.
Read-only REST access to the recces in your own workspace, with scoped keys you create and revoke in the console, and SAML single sign-on for Enterprise. Available on Team and Enterprise Packs.
- Your keyCreated in the console, scoped
- One workspaceA key can never read another
- Read the recordRecces, sections, Quality Score
- Your systemsJSON over HTTPS
Authentication
An admin creates keys in the console under Settings → API keys. The key is shown once, stored hashed, and scoped. It resolves to exactly one workspace — a key can never read another tenant. 600 requests per minute per key.
curl -H "x-api-key: rn_live_…" \ "https://sjklvobxgbwcghljixbd.supabase.co/functions/v1/public-api/v1/recces?limit=20"
Keys are created, scoped and revoked in the console under Settings → API keys, and every call is journalled against the key that made it. If a key leaks, revoking it is one action and takes effect immediately.
Keys are scoped and revocable, and every call is logged.
Illustrative diagram of the integrations screen.
Endpoints
| Endpoint | Scope | Returns |
|---|---|---|
| GET /v1/recces?since=<iso>&limit=<n> | read:recces | Recces in the workspace, newest first. `since` filters on last update. |
| GET /v1/recces/{id} | read:recces | One recce with every section, its officer and its Quality Score. |
Responses are { "data": … }. Errors: 401 invalid key · 403 scope required · 404 · 429 rate limited (with Retry-After).
Single sign-on
Enterprise workspaces sign in with SAML. Send us your identity provider metadata; we register the provider and give you a provider ID to enter under Settings → SSO with your verified email domain. New people from that domain are provisioned into the workspace on first sign-in with the role you choose.