canonical: https://jentic.com/apis/getclarify.ai/getclarify

# Getclarify Clarify API

The Clarify API manages the records, lists, and collaboration inside a CRM workspace, where every object holds records that an agent can create, update, merge, and relate to one another. Records can be grouped into lists that are published or exported as CSV, annotated with comments, and tracked through an activity trail, while object and record access grants control who can see each one. It also covers custom object schemas, file attachments on records, and meeting recordings and transcripts, all scoped to a workspace in the URL path.

## For AI agents

Create, update, and merge CRM records in a Clarify workspace, group them into lists, and manage comments, access grants, and attachments. Authenticates with an API key or a user access token.

## Scope

Does not process payments, send SMS, or host video meetings. Use for managing records, lists, and collaboration within a Clarify workspace only.

## Capabilities

- Create, update, and merge records within a workspace object
- Group records into lists and publish or export a list's rows as CSV
- Post comments on a record and read its activity trail
- Grant and revoke access to records and objects
- Define custom object schemas for a workspace
- Attach files to records and manage meeting recordings and transcripts

## Use cases

### Agent-Maintained CRM Records

An AI agent connected through Jentic creates and updates records inside a Clarify workspace object and merges duplicates it finds, so the CRM stays current without a person editing each record. Because records, their relationships, and their activity trail live behind the same workspace, the agent can read context before it writes.

Example prompt: Create a record in the given workspace object, then merge it with an existing duplicate if one is found

### List Building and CSV Export

A workflow groups records into a list, publishes it, and exports the list's rows as CSV for use elsewhere, turning a segment of CRM records into a shareable file. The list stays tied to its object, so the export reflects the records currently in it.

Example prompt: Create a list for this object, add the matching records, publish it, and export its rows as CSV

### Record Access Delegation

An operations workflow grants a teammate access to specific records and revokes it when the work is done, using the record and object access grant operations to keep visibility tight. This lets an agent hand out and pull back access without a workspace admin doing it manually.

Example prompt: Grant a teammate access to this record, then revoke the grant once the task is complete

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/workspaces/{workspace}/objects/{object}/records` | Create a record |
| GET | `/workspaces/{workspace}/objects/{object}/records/{id}` | Get a record |
| PATCH | `/workspaces/{workspace}/objects/{object}/records` | Update records in bulk |
| POST | `/workspaces/{workspace}/objects/{object}/records/{record}/merges` | Merge records |
| POST | `/workspaces/{workspace}/objects/{object}/lists` | Create a list |
| POST | `/workspaces/{workspace}/objects/{object}/lists/{list}/rows/csv` | Export a list's rows as CSV |
| POST | `/workspaces/{workspace}/comments` | Create a comment |
| POST | `/workspaces/{workspace}/schemas/objects` | Create a custom object |

## Key resources

- **Records** — Records within a workspace object, with create, update, merge, and bulk operations
- **Lists** — Lists that group records, can be published, and export their rows as CSV
- **Comments and Activities** — Comments on records and the activity trail tracked against them
- **Access Grants** — Object- and record-level access delegations that can be granted and revoked
- **Schemas** — Custom object schemas defined per workspace

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 55 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 36 / 100
  - Developer Experience & Jentic Compatibility: 45 / 100
  - AI-Readiness & Agent Experience: 57 / 100
  - Agent Usability: 87 / 100
  - Security: 55 / 100
  - AI Discoverability: 90 / 100
- **View full report:** https://jentic.com/apis/getclarify.ai/getclarify/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Clarify API by hand means choosing between an API key and a bearer user access token, carrying it in the Authorization header, and threading workspaces, objects, records, and lists together yourself. Through Jentic you install once, import Clarify from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Clarify puts the workspace id in the URL path (`/workspaces/{workspace}/...`), so a rule can pin your agent to one workspace: it can read and create records there and reach nothing outside it. You choose which operations it may call, so destructive ones like deleting records or revoking access grants are not included unless you add them.
- **Credential handling:** Your Clarify API key or access token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a CRM record' or 'export a list as CSV', and Jentic returns the matching Clarify operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Attio API** — CRM built on the same objects, records, and lists model
- **Close CRM API** — Sales CRM focused on leads, calls, and pipeline
- **Copper API** — CRM for contacts and pipeline integrated with Google Workspace
- **Clearbit API** — Enriches company and contact data for the records you store

## FAQ

### Is there a Clarify MCP server?

You don't need an MCP server to give your agent the Clarify API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent can create records, build lists, and read activity straight away, with no extra server to run and no tool definitions to load into the agent's context.

### Can I limit what my agent is allowed to do with the Clarify API?

Yes. Write a rule that allows only the record read and create operations under one workspace id, so the agent can add and read records in that workspace and touch nothing else, and every call it makes is logged. Destructive operations like deleting records or revoking access grants are left out unless you add them.

### What authentication does the Clarify API use?

The Clarify API accepts two credentials per its OpenAPI spec: an API key sent in the Authorization header, and a bearer user access token also sent in the Authorization header, where some person-acting endpoints accept only the bearer token. Through Jentic the credential is stored encrypted by your own instance and injected at call time, so it never appears in the agent's prompt or logs.

### Can I export a Clarify list as CSV?

Yes. You group records into a list, publish it, and then call the operation that exports the list's rows as CSV, so a segment of CRM records becomes a shareable file. The export reflects the records currently in the list under that object.

### What are the rate limits for the Clarify API?

The OpenAPI spec does not specify rate limits for the Clarify API. For current limits and token details, see the Clarify documentation at https://www.clarify.ai.

### How do I keep CRM records current through Jentic?

Import the Clarify API from the Jentic API Directory, then have your agent issue a request such as 'create a record in this workspace object'. Jentic matches the intent to the create-record operation and returns its input schema so the agent sends the right fields, with your stored credential injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.