Reference

Authentication with API keys

Create a workspace API key (om_live_…), send it as Authorization: Bearer on the regular REST API.

October 14, 2026 4 min read

Create a key in the dashboard under Settings → API Keys (or AI Connections for assistant keys). The full key — om_live_… — is shown once; it is stored hashed.

Send it on every request: Authorization: Bearer om_live_… The key acts as the person who created it, with that person's current role, inside that workspace only — never as an admin of anything else. Account-level areas (sign-in, billing, workspace settings, agency tools) always need a person signed in and never work with a key.

Scopes

Each key carries scopes like contacts:read or deals:write. A GET needs <resource>:read, anything else <resource>:write — for example GET /api/v1/crm/contacts needs contacts:read. The live list is at GET /api/v1/developers/scopes.

Test your key

GET /api/v1/developers/me returns the workspace and key you are acting as — the same call Zapier and Make use as their connection test.