Cloze CRM API

Name: Cloze CRM API API
Brand: Cloze CRM API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact ManagementapiKey43 EndpointsREST

For Agents

Manage Cloze CRM data programmatically — create and update people, companies, and projects, log timeline communications, query funnel analytics, and subscribe to change webhooks.

Quickstart

Get started with Cloze CRM API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a person in CRM"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Cloze CRM API API.

Create, update, find, and delete people and company contact records

Create and update projects, including stages, segments, and custom fields

Log communications, content, and to-do items on a contact or project timeline

Query analytics endpoints for team activity, lead qualification, and funnel data

GET STARTED

Start building with Cloze CRM API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Cloze CRM API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Cloze CRM API, keeping it validated and agent-ready. The Cloze API gives programmatic access to the Cloze relationship management platform: people, companies, projects, the activity timeline, custom fields, segments, stages, team roles, analytics, and webhooks. It supports creating and updating contacts and companies, recording communications and content against a timeline, querying project funnels and lead qualification data, and subscribing to change events. Authentication uses an API key passed as the api_key query parameter.

Use Cases

Patterns agents use Cloze CRM API API for, with concrete tasks.

★ Two-Way Contact Sync With Other Systems

Teams running Cloze alongside marketing automation or finance tools sync contacts both ways. /v1/people/find and /v1/companies/find detect existing records before /v1/people/create or /v1/companies/create insert new ones, while /v1/people/update keeps fields current as upstream systems change. Webhook subscriptions via /v1/webhooks/subscribe push change events outwards, removing the need to poll. The 43 endpoints cover the full read-write surface needed for a robust sync.

Find a person in Cloze by email via GET /v1/people/find, and if no match exists, create the record via POST /v1/people/create with name, email, and company

Automated Timeline Logging From Email and Calls

Sales reps want every email, call, and meeting to land on the right contact's timeline without manual entry. POST /v1/timeline/communication/create records inbound and outbound communications against a person or company, and POST /v1/timeline/content/create attaches related content like decks or notes. Combined with /v1/people/find for resolution, an integration can listen on a mail server or telephony API and write a complete activity history into Cloze automatically.

When a sales call ends, find the contact in Cloze by phone number then POST /v1/timeline/communication/create with the call duration, direction, and a short summary

Sales Funnel and Lead Qualification Analytics

Sales managers analysing pipeline health pull funnel and lead qualification data on demand rather than waiting for built-in reports. POST /v1/analytics/funnel returns funnel stage data, POST /v1/analytics/leads returns lead qualification metrics, and POST /v1/analytics/teamactivity surfaces what the team did in a given period. The results power a custom dashboard or feed a weekly forecasting report without exporting to spreadsheets.

Run POST /v1/analytics/funnel for the current quarter and POST /v1/analytics/leads for the same period, then summarise stage-by-stage conversion rates

AI Agent Maintaining a Live CRM via Jentic

AI agents handling sales operations call Cloze through Jentic to keep records current as conversations happen. The agent expresses an intent like 'create a person' or 'log a call', and Jentic loads the matching Cloze operation, supplies the api_key from the vault, and returns structured results. The same flow handles webhooks, so the agent can react to changes without polling the Cloze feed endpoints.

Through Jentic, search for 'create a person in CRM', load the cloze.com /v1/people/create operation, and execute it with the prospect's name, email, and company

Key Endpoints

43 endpoints — jentic publishes the only available openapi specification for cloze crm api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/people/create

Create a person record

POST

/v1/people/update

Update a person record

GET

/v1/people/find

Find people by email or other identifier

POST

/v1/companies/create

Create a company record

POST

/v1/projects/create

Create a project

POST

/v1/timeline/communication/create

Add a communication record to a timeline

POST

/v1/webhooks/subscribe

Subscribe to change events

POST

/v1/analytics/funnel

Query funnel information (BETA)

POST

/v1/people/create

Create a person record

POST

/v1/people/update

Update a person record

GET

/v1/people/find

Find people by email or other identifier

POST

/v1/companies/create

Create a company record

POST

/v1/projects/create

Create a project

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Cloze api_key is stored encrypted in the Jentic vault (MAXsystem) and appended as a query parameter only at execution time. The agent never sees the raw key, and it is not written into prompt history.

Intent-based discovery

Agents search by intent (e.g. 'create a person', 'log a call', 'query sales funnel') and Jentic returns the matching Cloze operation with its input schema, so the agent can call /v1/people/create, /v1/timeline/communication/create, or /v1/analytics/funnel without browsing the Cloze docs.

Time to first call

Direct Cloze integration: 2-3 days to wire up create/update/find for people and companies plus webhook subscription handling. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Pipedrive API

Pipedrive is a sales-focused CRM with a similar contact, deal, and activity model

Choose Pipedrive when the team uses its visual sales pipeline UI; choose Cloze when relationship management and timeline auto-capture are the priority

Alternative

Copper API

Copper is another relationship-management CRM with people, companies, opportunities, and activities

Choose Copper for tight Google Workspace integration; choose Cloze when funnel analytics and webhook subscriptions are required

Complementary

HubSpot API

HubSpot covers marketing automation and email that complements Cloze's relationship-management focus

Use HubSpot for outbound email and forms, then mirror engagement back to Cloze via /v1/timeline/communication/create

FAQs

Specific to using Cloze CRM API API through Jentic.

Why is there no official OpenAPI spec for Cloze CRM API?

Cloze does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cloze CRM API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Cloze CRM API use?

The Cloze API uses an apiKey scheme with the key passed as the api_key query parameter on every request. Through Jentic the key is stored encrypted in the vault and appended to the request URL only at execution time, so the agent never sees the raw key.

Can I create and update people and companies with the Cloze CRM API?

Yes. POST /v1/people/create and POST /v1/people/update handle person records, POST /v1/companies/create and POST /v1/companies/update handle companies, and DELETE /v1/people/delete removes a person. /v1/people/find and /v1/companies/find let you check for existing records before inserting.

Can I subscribe to webhooks for Cloze changes?

Yes. POST /v1/webhooks/subscribe registers a callback URL for change events on people, companies, and projects. POST /v1/webhooks/unsubscribe removes a subscription, and GET /v1/webhooks lists active subscriptions.

What are the rate limits for the Cloze CRM API?

The OpenAPI specification does not declare explicit rate limit headers or a 429 response. Cloze applies plan-based limits, so high-volume sync jobs should batch updates and back off if requests start to fail. Through Jentic, retries are handled by the SDK.

How do I create a person record in Cloze through Jentic?

Install the SDK with pip install jentic, search for 'create a person in CRM', load the cloze.com /v1/people/create operation, and execute it with name, email, and company. Jentic supplies the api_key automatically and returns the created record's identifier.

Can I query Cloze analytics endpoints from an integration?

Yes. POST /v1/analytics/teamactivity, /v1/analytics/activity, /v1/analytics/projects, /v1/analytics/leads, and /v1/analytics/funnel return team-, project-, lead-, and funnel-level metrics that can drive a custom dashboard or feed into a weekly report.