REST API, MCP and webhooksNEW
Integrate and automate with engineering discipline: a key-authenticated REST API v1 and a native MCP server that connects your AI agent straight to the CRM, so it can discover objects, read and write records and push leads and contacts. Plus a per-minute rate limit, usage metrics and webhooks to react to events.
- REST API v1 by key
- Native MCP server for your AI agent
- Rate limit, usage metrics and webhooks
Authenticated REST API v1
Integrate any system with a REST API protected by key. You connect the CRM to your stack with no middleman.
Per-minute rate limit
A per-minute limit and rate-limit headers protect the platform and guide your retries. The integration stays stable under load.
Usage metrics per key
Track each key’s consumption to govern SLA and spot abuse. You know who calls what and how much.
Event webhooks
Receive events in near real time and trigger external flows. Your systems react without polling the API.
Native MCP server
Connect your AI agent straight to the CRM through the native MCP server: same key, rate limit and permissions (RBAC) as the API. See the Developers page.
Native MCP server: connect any AI agent to the CRM
Same key and tenant scope across REST and MCP
Best-effort webhooks that don’t block the CRM
Connect your AI agent
The native MCP server lets your agent discover objects and fields, read and write records and push leads and contacts, with the same key, rate limit and permissions (RBAC) as the API. See it all on the Developers page.
Integrate and react to events
Read and write records of any object over REST, with a per-minute limit and usage metrics. Webhooks fire to your systems when something changes, without ever disrupting saving.
- 1
Generate an API key in Settings → API & keys.
- 2
Call REST API v1 or connect your agent via the MCP server.
- 3
Subscribe to webhooks for the events that matter.
- 4
Track usage metrics per key to govern the SLA.
Connecting an AI agent
Point your agent at the MCP server and it discovers objects, pushes leads and contacts and automates, with no integration code.
Syncing with the ERP
REST API v1 exchanges accounts and orders with the ERP using a dedicated, monitored key.
Reacting to a new deal
An event webhook notifies an external system the moment a deal changes stage, no polling.
What is the native MCP server?
It's a server that connects your AI agent straight to the CRM, letting it discover objects and fields, read and write records, and push leads and contacts.
Does the REST API require authentication?
Yes. REST API v1 is authenticated by key, protecting access for any system you connect.
Is there a limit on calls per minute?
Yes. There's a per-minute rate limit with its own headers, to protect the platform and guide your retries.
Can I track how much each key is being used?
Yes. Usage metrics per key show consumption, helping you govern SLA and spot abuse.
How do my systems find out when something changes in the CRM?
Webhooks fire events in near real time, so your systems react without constantly polling the API.
Can a slow webhook block a record from saving?
No. Webhooks run best-effort and never disrupt saving in the CRM.
Does the AI agent connected via MCP have the same permissions as the API?
Yes. MCP uses the same key, rate limit and permissions (RBAC) as the REST API.
Can my AI agent push leads and contacts straight into the CRM?
Yes. Through the MCP server, the agent discovers objects and pushes leads and contacts with no integration code needed.
Can I sync the CRM with an ERP using the API?
Yes. REST API v1 exchanges accounts and orders with the ERP using a dedicated, monitored key.