Close CRM API

Name: Close CRM API API
Brand: Close CRM API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMDeal Pipelinebasic, oauth236 EndpointsREST

For Agents

Manage Close CRM leads, contacts, opportunities, activities, tasks, and pipelines so agents can read and write the full sales workflow programmatically.

Quickstart

Get started with Close 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 lead in close crm"

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

Capabilities

What an agent can do with Close CRM API API.

Create, update, and merge leads alongside their embedded contact records

Move opportunities through pipeline stages and update value, status, and confidence

Log calls, emails, notes, and other activity types against a lead's timeline

Create, assign, and complete tasks for sales reps tied to a specific lead

GET STARTED

Start building with Close CRM API API

Explore with Jentic

View OpenAPI Document

Use for: Create a new lead in Close CRM with company and contact details, Update a contact attached to an existing lead, Move an opportunity to the 'Closed Won' stage with a final value, Log a call activity against a specific lead

Not supported: Does not handle email sending infrastructure, dialler hardware, or marketing automation campaigns — use for managing leads, opportunities, activities, and pipelines inside Close CRM only.

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

Jentic publishes the only available OpenAPI specification for Close CRM API, keeping it validated and agent-ready. The Close CRM API exposes the full sales workflow used by inside-sales teams: leads with embedded contacts, opportunities tracked through pipelines, activities such as calls and emails, tasks, users, organisations, and custom fields. You can list and filter leads, push updates from external systems, log activities programmatically, and reshape pipelines as a sales motion evolves. The API uses HTTP basic auth with the API key as the username, or OAuth 2.0 for partner integrations.

Use Cases

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

★ Form-to-Lead Capture

Convert website form submissions into Close CRM leads in real time. The agent receives the form payload, calls POST /lead/ with a contact, organisation, and source custom field, then routes the lead to the right pipeline. Sales reps see the new lead in their inbox within seconds rather than waiting for nightly Zapier syncs.

Call POST /lead/ with name, contacts (email, phone), and a custom field setting source='Website Form', then return the new lead_id.

Pipeline Stage Automation

When an external system signals that a deal has progressed (e.g. contract signed in a CLM tool), automate the matching update in Close. The agent calls PUT /lead/{lead_id}/ to update the opportunity stage and value. Combined with custom fields, this keeps the pipeline accurate without reps clicking through the UI.

Call PUT /lead/{lead_id}/ with the opportunity status set to 'Closed Won' and the value updated to the contract amount.

Activity Logging from Outside Tools

Surface non-Close communications (e.g. WhatsApp messages, in-app chats, support tickets) on the Close lead timeline so reps see the full picture. The agent calls GET /activity/ to enumerate types, then POSTs structured note or call activity records to the relevant lead. This keeps Close as the single source of truth for customer interaction history.

POST a note activity to a lead's timeline whenever a WhatsApp message arrives, including the message body and timestamp.

Daily Smart-View Digest

Send each rep a morning digest of leads they need to act on by querying Close's filtered lead list. The agent calls GET /lead/ with a smart-view query string, formats the matching leads into a chat or email, and links each entry back to its Close URL. This replaces manual smart-view checking and ensures nothing falls through the cracks.

Call GET /lead/ with a query string filtering opportunities in 'Negotiation' and post the resulting leads to the rep's Slack DM.

Agent-Driven CRM Updates via Jentic

Connect Close to an AI assistant through Jentic so a rep can say 'log a 15-minute call with Acme Corp and set a follow-up task for Friday' in chat. The assistant searches Jentic for the right Close operations, loads the schemas, and executes them with the API key kept in the Jentic vault. The Close API key never enters the assistant's prompt or response.

Use the Jentic Python SDK to search for 'log call activity', load the matching Close operation, and execute it with lead_id, duration, and direction.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/lead/

List or filter leads

POST

/lead/

Create a new lead

PUT

/lead/{lead_id}/

Update an existing lead

POST

/lead/merge/

Merge two duplicate leads

GET

/contact/

List contacts

POST

/contact/

Create a new contact

GET

/activity/

List or filter activities

GET

/lead/

List or filter leads

POST

/lead/

Create a new lead

PUT

/lead/{lead_id}/

Update an existing lead

POST

/lead/merge/

Merge two duplicate leads

GET

/contact/

List contacts

POST

/contact/

Why though Jentic?

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

Credential isolation

Your Close API key (or OAuth client credentials) are stored encrypted in the Jentic vault and injected into the Authorization header at execution time. Agents receive scoped tokens, so the API key never appears in prompts, model context, or logs.

Intent-based discovery

Agents search Jentic by intent (e.g. 'create a lead' or 'log a call') and Jentic returns the matching Close operation with its input schema, so the agent can call the right endpoint without browsing developer.close.com.

Time to first call

Direct Close integration: 1-2 days to handle pagination, smart-view queries, custom fields, and rate-limit backoff. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

HubSpot

Larger CRM platform with marketing, sales, and service hubs and a wider API surface area.

Choose HubSpot when the agent also needs marketing automation or service-desk workflows alongside the sales CRM.

Alternative

Pipedrive

Sales pipeline CRM with deals, persons, organisations, and activities.

Choose Pipedrive when the team prefers a deal-first pipeline UI rather than Close's lead-centric model.

Alternative

Salesforce

Enterprise CRM platform with deep customisation, multi-cloud product breadth, and global scale.

Choose Salesforce when the agent needs enterprise CRM with custom objects, complex sharing rules, or AppExchange integrations.

Complementary

Twilio

SMS and voice provider commonly used to power calls logged back into Close.

Use alongside Close when the agent needs to send SMS or place programmable calls and log the result on the lead timeline.

FAQs

Specific to using Close CRM API API through Jentic.

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

Close publishes HTML reference docs at developer.close.com but does not export a downloadable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Close 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 Close CRM API use?

The API supports HTTP Basic Auth with your Close API key as the username and an empty password, and OAuth 2.0 authorisation code flow for partner integrations. Through Jentic the API key (or OAuth tokens) are stored encrypted in the vault, and only scoped tokens reach the agent's context.

Can I merge duplicate leads with the Close CRM API?

Yes. Call POST /lead/merge/ with the source and destination lead IDs. Close moves all contacts, activities, tasks, and opportunities to the destination lead and deletes the duplicate. This is the same operation surfaced in the Close UI's merge modal.

What are the rate limits for the Close CRM API?

Close enforces a per-account rate limit (typically 240 requests per minute) and burst limits per endpoint. When approaching the limit, the API returns 429 with a Retry-After header. Through Jentic, watch this header and back off accordingly when bulk loading leads.

How do I log a call activity through Jentic?

Search Jentic for 'log call activity' and the matching Close operation under POST /activity/call/ is returned with its schema for lead_id, contact_id, direction, and duration. Load the operation, then execute it with the call details. The standard quickstart is pip install jentic, search, load, execute.

Is the Close CRM API free?

API access is included with all paid Close subscriptions; there is no separate per-call charge. The free trial includes API access for evaluation, but production use requires an active Close seat.