Close CRM API

Name: Close CRM 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.

Install Jentic One Beta

Connect the Close CRM API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Close CRM API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi.close.com%2Fclose" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi.close.com%2Fclose" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Close CRM 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

GET STARTED

Start building with Close CRM API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Close CRM 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 your Jentic One instance. 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 Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Close CRM API by hand means choosing between its basic and OAuth 2.0 auth, targeting the v1 host, and mapping the lead, contact, and activity routes yourself. Through Jentic you install once, import Close from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Close puts the lead id in the URL path (/lead/{lead_id}/), so a rule can pin your agent to one lead: it can update that lead and nothing else. You choose the operations it may call, so actions like merging leads are only included if you add them.

Credential isolation

Your Close API key or OAuth client credentials are stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a lead' or 'log a call', and Jentic returns the matching Close operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Close CRM 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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Close CRM API?

Yes. Because you run Jentic One yourself, your own rules decide which Close operations and credentials the agent may use. Since Close puts the lead id in the URL path (/lead/{lead_id}/), a rule can pin the agent to a single lead so it can update that lead and nothing else, and you choose exactly which operations it may call. High-impact actions like POST /lead/merge/ are only reachable if you explicitly add them to the agent's allowed set.

Close CRM API

Connect the Close CRM API to your agent

Capabilities

Start building with Close CRM API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs