The Clarify API lets you read and write your Clarify data programmatically - records (People, Companies, Deals, and Custom Objects), workspace users, and meeting data. Use it to sync data with external systems, build custom integrations, and automate work across your stack.
Deciding between the API, agents, connectors and Zapier? Automating Clarify and connecting your stack compares the options before you commit to one.
Key types
Clarify has two API key types. Which one you need depends on what you're building.
Personal - acts on your behalf and reaches the same data you can see in Clarify. Any workspace member can create one. Use this type for MCP.
Workspace - a shared key, scoped to the workspace's public data. It carries no user identity, which changes what meeting and email data it can read. Only workspace admins can create one.
Create a key
Click Create API key
Enter a Name of up to 64 characters
Choose a Type, then click Create
Copy the key straight away. It isn't shown again
💡 No Type dropdown? The selector only appears when both types are available to you. Workspace keys are admin-only, so a member sees no selector and gets a Personal key. Admins see the dropdown, which defaults to Personal; change it to Workspace if you're building a shared integration rather than acting as yourself.
What you see in the list depends on your role. Admins see every key in the workspace, along with who created it and when it was last used. Members see only their own personal keys.
Authenticate your requests
Send the key in the Authorization header using the api-key scheme. This is not a Bearer token, and most HTTP clients and AI agents default to Bearer unless you tell them otherwise.
Authorization: api-key YOUR_API_KEY
Connect an AI assistant
Clarify hosts a Model Context Protocol (MCP) server, so an MCP-compatible client such as Claude or Cursor can call the API directly. Point your client at https://api.clarify.ai/mcp and send two headers:
Authorization: api-key YOUR_API_KEY
X-Clarify-Workspace: your-workspace
⚠️ MCP accepts personal keys only. Send a workspace key and the connection itself succeeds, so your client will list every tool as though it is working. Each tool call is then refused with "This API key cannot access MCP. Use a personal API key instead; create one in workspace settings." A workspace key is not a workaround here - you need a personal one. A workspace key also carries no personal identity, so it reaches only what is shared with the whole workspace. It cannot open a record or list that is private to its owner. See Sharing and permissions.
Meeting and email data
A key reaches the meeting and email data its identity can see, so the key type matters more here than anywhere else.
A personal key carries your identity. It reaches the meetings and emails you can already see in Clarify, and no more.
A workspace key carries no user identity, so the protected fields come back empty rather than erroring: email subjects and bodies, and meeting notes, summaries and descriptions. Requesting a recording's artifacts returns a no-access error. Unprotected fields still populate, including meeting titles, times and participants, so a response can look complete while the content is blank. To open the protected fields to a workspace key, an admin can set Emails or Meetings to Everyone under Settings → Workspace → Email and meetings; the two are independent. Either also makes that data visible to every member of the workspace, so prefer a personal key where you can. See Email and meetings for the full visibility model.
Recordings and transcripts come back as signed download links that expire after about a day, and either link is empty when that file isn't available. Fetch them when you need them rather than storing the links.
Common issues
Requests return an authentication error
Check the scheme before anything else. Authorization: Bearer YOUR_API_KEY fails; Authorization: api-key YOUR_API_KEY is correct. If you've lost the key, create a new one - existing keys can't be revealed again.
MCP says the key can't access it
You're using a workspace key. Create a personal key and use that instead.
Documentation
Guides and getting started: developer.clarify.ai/docs
Full API reference: developer.clarify.ai/docs/api-reference
Building with an AI assistant? Point it at developer.clarify.ai/llms.txt
The API continues to evolve. Questions or issues? Reach out to support through the in-app messenger.