canonical: https://jentic.com/apis/close.com/close # Close CRM API 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. ## For AI agents Create and update leads, contacts, opportunities, and activities in Close, run sequences, and read smart views for sales pipeline automation. ## Scope Does not handle marketing email blasts, support ticketing, or contract e-signature - use for sales CRM, lead management, and outbound cadences only. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'log a close email activity', load the schema, and execute it for a follow-up email to lead L42. ## Key endpoints | 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 | ## Key resources - **Leads** — Account-level records grouping contacts, opportunities, and activities - **Contacts** — Individual people associated with a lead - **Opportunities** — Revenue records with values and pipeline stages - **Activities** — Calls, emails, notes, meetings, SMS, and tasks logged against leads - **Pipelines** — Stage definitions used by opportunities - **Sequences** — Multi-step outbound cadences across email and SMS - **Smart Views** — Saved filters for slicing the lead database - **Custom Fields** — Per-org custom attributes on leads, contacts, and opportunities ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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 - **Clockify API** — Time tracking platform to log billable activity against Close customer accounts. - **Clockwork Recruiting API** — Executive search ATS that pairs with Close to manage employer-side relationships. - **Closum API** — Marketing automation platform to nurture leads above the Close pipeline. ## FAQ ### 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.