Skip to main content
All requests to the Automate CRM Integration API require authentication via workspace API keys. The key securely associates your request with your CRM organization and enforces granular permissions.

Authentication headers

Include your API key in the x-api-key header with every HTTP request:
Authentication is strictly header-based. Never pass API keys as URL query parameters.

Required permission scopes

API keys are configured with specific scope capabilities. Ensure that your key has the appropriate scope assigned:
  • crm:read: Required for all read operations, including GET, HEAD, and OPTIONS.
  • crm:write: Required for all state changes and mutations, including POST, PATCH, PUT, and DELETE.
If a request is sent with an API key lacking the necessary scope, the server rejects the call with HTTP 403 Forbidden:

Code examples

Security recommendations

Keep your API keys secret. Never embed API keys directly in client-side code, mobile applications, or public Git repositories. Use server-side proxies or backend microservices to communicate with the CRM API.