Skip to main content
Apocor uses an OAuth client-credentials flow. You exchange an API key for a short-lived bearer token, then send that token on every request. Apocor keys are the only credential you manage — all upstream providers are handled for you.

The flow

Test vs live keys (same API host)

Same host, separate data partition and separate sandbox webhook paths. See Webhooks.

1. Get your API key

Your Apocor contact provisions an API key from the dashboard. The secret is returned only once — store it in a secret manager.

2. Get an access token

Tokens are valid for 1 hour (expires_in: 3600). Request a new one when it expires — there is no refresh token in the client-credentials flow.

3. Call authenticated endpoints

Roles & access

Every key and user carries a role that scopes what it can see and do.
Requests are always scoped to the caller’s organization (and, for resellers, its children). You can only ever read or write resources your token is entitled to.

Errors

A missing or invalid credential returns 401 with a stable code:
See Error codes for the full list.