Authentication
Authenticate with the Talonic API using Bearer tokens: API keys prefixed tlnc_ carry scopes like extract, read, write, and billing that gate access.
Talonic API authentication uses Bearer tokens: every request carries an API key in the Authorization header. Keys are prefixed tlnc_, are scoped per workspace, and carry a set of scopes that determine which operations they can perform. Create and manage keys from Settings → API Keys in the dashboard, or programmatically via POST /v1/account/keys.
Authorization header
curl https://api.talonic.com/v1/documents \
-H "Authorization: Bearer $TALONIC_API_KEY"API Key Scopes
Each API key carries one or more scopes that determine which operations it can perform. New keys default to extract, read, write, and operations.
Available scopes
POST /v1/extract, POST /v1/documents/:id/re-extract).POST /v1/billing/topup). Not included by default; add explicitly when creating the key.New keys default to extract, read, write, and operations. The billing and delivery scopes must be added explicitly. If a request requires a scope your key does not carry, the API returns 403 with error code insufficient_scope and lists the required scopes in the response body.
DELETE /v1/account/keys/:keyId and mint a replacement.