Close CRM API
37
AI ReadinessNon-Ready (F)37/100
Agent-ready OpenAPI document · curated by JenticCRMDeal Pipelinebasic131 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Create and update leads, contacts, opportunities, and activities in Close, run sequences, and read smart views for sales pipeline automation.
Use for: I want to create a new lead with two contacts in Close, Log a call activity for a lead from yesterday, Move an opportunity from Discovery to Proposal stage, Enrol a list of leads into a follow-up email sequence
Not supported: Does not handle marketing email blasts, support ticketing, or contract e-signature - use for sales CRM, lead management, and outbound cadences only.
Jentic publishes the only available OpenAPI specification for Close CRM API, keeping it validated and agent-ready. Close is a sales CRM aimed at high-velocity inside sales teams, combining lead and contact management with built-in calling, email sequences, SMS, and a power dialer. The API exposes 131 operations across leads, contacts, opportunities, activities (calls, emails, notes, meetings, SMS), pipelines, custom fields, sequences, smart views, and bulk actions. Authentication is HTTP Basic with the API key as the username.
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.
1
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%2Fclose.com%2Fclose" | sh2
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%2Fclose.com%2Fclose" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 and update leads with multiple contacts, opportunities, and custom fields
Log calls, emails, notes, meetings, and SMS as activities against a lead
Move opportunities through pipeline stages with status updates
Enrol leads into multi-step email and SMS sequences
Query smart views to filter leads by saved sales criteria
Trigger bulk actions on filtered lead sets and track export jobs
Use Cases
Patterns agents use Close CRM API for, with concrete tasks.
★ Inbound Lead Routing and Enrichment
Inbound forms produce raw lead records that need enrichment, deduplication, and routing in seconds. POST /lead/ creates the lead, POST /contact/ attaches contacts, and PUT /lead/{id}/ patches the record with enrichment data and assigns the right user. The flow replaces brittle Zaps and lets sales engineering own the routing logic.
Create a lead for 'Acme Corp' with contact Jane Doe (jane@acme.com), assign to user U9, and set the lead_status to 'Working'.
Activity Logging from Calling and Email Tools
Reps using external dialers or email clients still need every touch logged in Close. POST /activity/call/ records a call with duration, direction, and notes; POST /activity/email/ logs an email; POST /activity/sms/ logs an SMS. This produces a complete activity timeline without forcing reps to switch tools.
Log a 12-minute outbound call for lead L42, with note 'Demo scheduled for 2026-06-15' and direction 'outbound'.
Sequence-Driven Outbound Cadences
Outbound teams run multi-step cadences that combine email, SMS, and call tasks. The Sequences endpoints let an agent enrol qualified leads from a smart view into the right cadence, while activity endpoints surface replies and call outcomes. Teams can codify their best playbook once and replay it across territories.
Pull all leads in the 'Q3 SMB Outbound' smart view and enrol them in the 'SMB 5-Step Outreach' sequence, starting tomorrow.
AI Agent Sales Co-Pilot
Pair Close with an AI assistant that summarises deals, drafts follow-ups, and books meetings. Through Jentic, the agent searches by intent, loads the right operation, and updates the CRM without seeing the rep's API key. The Basic auth credential lives in your Jentic One instance and never enters the model context.
Search Jentic for 'log a close email activity', load the schema, and execute it for a follow-up email to lead L42.
Key Endpoints
131 endpoints — jentic publishes the only available openapi specification for close crm api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/lead/
Create a lead
GET
/lead/{id}/
Retrieve a lead by id
PUT
/lead/{id}/
Update a lead
POST
/contact/
Create a contact
POST
/activity/call/
Log a call activity
POST
/activity/email/
Log an email activity
POST
/activity/note/
Add a note to a lead
POST
/lead/
Create a lead
GET
/lead/{id}/
Retrieve a lead by id
PUT
/lead/{id}/
Update a lead
POST
/contact/
Create a contact
POST
/activity/call/
Log a call activity
POST
/activity/email/
Log an email activity
POST
/activity/note/
Add a note to a lead
Jentic AI Readiness Score
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.
C
Close CRM API
- Non-Ready (F)37/100
43
Foundational Compliance63
Developer Experience & Jentic Compatibility53
AI-Readiness & Agent Experience75
Agent Usability10
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
43
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
73%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
53
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
46%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
65%
Summary Coverage
Coverage of summaries across operations/tags/info.
75
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A-Signals: 1
75%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
10
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
10%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Close by hand means assembling its HTTP Basic header from the API key, mapping its lead, contact, and activity endpoints, and handling retries yourself against api.close.com/api/v1. Through Jentic you install once, import the Close CRM API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Close puts the lead id in the URL path (/lead/{id}/), so a rule can pin your agent to one lead: it can read and update that lead and nothing else. You choose the operations it may call, so logging calls, emails, or notes are not included unless you add them.
Credential isolation
Your Close API key is stored once, encrypted, by your own Jentic One instance and injected as the Basic Auth username at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a lead in Close', and Jentic returns the matching Close operation with its input schema, so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Close CRM API through Jentic.
Why is there no official OpenAPI spec for Close CRM API?
Close does not publish an OpenAPI specification - only narrative reference docs. 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?
Close uses HTTP Basic Auth where your API key is the username and the password is left empty. Through Jentic, the API key is stored encrypted in your Jentic One instance and injected into the Authorization header at execution time so agents never see the raw key.
Can I log a call activity with the Close CRM API?
Yes. POST to /activity/call/ with lead_id, direction, duration, and note. The endpoint returns the activity id and timestamps. For email and SMS, use /activity/email/ and /activity/sms/ with the analogous payloads.
What are the rate limits for the Close CRM API?
Close enforces per-organisation rate limits - typically 60 requests per second with burst allowances, returning 429 when exceeded. The spec does not encode exact thresholds. Jentic surfaces 429 responses to the agent so it can pace bulk imports and sequences.
How do I enrol leads in a sequence through Jentic?
Run pip install jentic, search for 'enrol lead in close sequence', load the relevant Sequences operation, and execute with sequence_id and lead_ids. To target a saved filter, first call the Smart Views endpoint to fetch the lead ids.
Does the Close CRM API support custom fields?
Yes. The Custom Fields endpoints let you read and write custom attributes on leads, contacts, and opportunities. Reference custom fields by their slug when patching records via PUT /lead/{id}/ or PUT /contact/{id}/.
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/{id}/), you can pin the agent to a single lead so it only reads and updates that record and nothing else. You also choose exactly which operations it may call, so activity endpoints like POST /activity/call/, /activity/email/, and /activity/note/ stay off-limits unless you explicitly add them.
GET STARTED