Custom integrations that move data between Ambit and the tools you use.
An API key gives a script, an automation, or another piece of software the ability to read from and write to your Ambit workspace. It's how you stitch Ambit into a larger setup — your CRM, a custom dashboard, a workflow automation tool.
Common use cases
Sync new contacts to your CRM. When a lead books a call, a script pulls the contact and creates the corresponding record in your CRM.
Send custom notifications. Send a Slack message to a specific channel whenever a high-value lead books.
Build reports. Pull funnel data into a custom dashboard alongside metrics from your other tools.
Pre-fill data from another system. Use details about a lead you already have to skip parts of your qualification.
If a tool you use can call an HTTP endpoint with a token, it can use the Ambit API.
What the API can access
An API key gives access to the data in the workspace it was created in:
The contacts in that workspace
The funnels and their structure
The bookings on the calendar
The exact endpoints and shapes available are covered in our API reference.
Security
Treat an API key like a password. Anyone who has the key has the access. Store keys in a secure location (a secrets manager, a vault, environment variables — not a file in source control), and revoke any key you're worried about.
Where to go next
How do I create an API key?
How do I revoke an API key?