Skip to main content

​
REST API keys

Send the workspace API key in the authorization header:
An admin creates and revokes keys through Integrations. Review the scopes selected during creation; do not assume a key can read contact data merely because it can read leads.

​
MCP OAuth

Authorize through the browser flow opened by your client. Select workspaces and approve the actions available to your current account permissions. A tool call must satisfy token scopes, the stored grant, current workspace membership, role, and product access. OAuth refresh does not expand consent. Reauthorize to add workspaces or permissions. Losing access to the default workspace does not silently switch requests to another workspace.

​
Supported scopes

A scope authorizes a capability; it does not imply that every capability is a REST endpoint. Read the endpoint or MCP tool contract for its required combination. Contact enrichment also needs leads:read and leads:contact_read. Delivery needs integrations:deliver and leads:contact_read. ICP and Signal Brief updates need both icp:read and icp:manage. Without contact permission, contact fields and profile URLs are redacted. Audience analytics returns aggregate information rather than individual contacts. Request only what your integration needs, and review the actual scopes on each key or OAuth grant.