API review

Close API review

Calling- and email-first sales CRM for SMB sales teams, with a lead-centric REST API v1 (OpenAPI since 2026-04), advanced filtering, bulk actions, a 30-day event log, webhooks with filters, AI field enrichment and an official remote MCP server. Best for inside-sales teams that call and email from the CRM.

Verified 25 Oct 2026 · 12 endpoints listed · Official MCP server

What a call costs

The actions you pay for, as Close prices them.

ActionCostPer
Call recording + transcription add-on$50/month per org + $0.02per minute
Phone lines (BYOL or rent)from $1per line/month
Calling and SMSpassed through at cost; most outbound calls ~ $0.02per minute
Additional organization$50 (Growth and Scale include 1 free secondary org)per org/month

Pricing, plan by plan

US dollars, as Close's pricing page shows them on 25 Oct 2026. Monthly and annual billing are shown apart.

Free tier No free plan. 14-day free trial, no credit card; includes $5 of calling and enrichment credits plus AI credits. Signup requires a phone number and consent to calls/texts (hands-on). Account pauses when the trial ends. 30-day money-back guarantee on paid plans.

Solo

$19/mo

billed monthly

$9/mo

billed annually

limited to 1 user; 500 AI credits/month (refreshes monthly, no rollover; more can be bought)

API included
Plan details

additional AI credits available for purchase (price not published on the pricing page)

Essentials

$49/mo

billed monthly

$35/mo

billed annually

1,000 AI credits per user/month, shared pool up to 10,000/month, no rollover; call recording retention 30 days

API included
Plan details

additional AI credits available for purchase (price not published on the pricing page)

Growth

$109/mo

billed monthly

$99/mo

billed annually

1,500 AI credits per user/month, shared pool up to 15,000/month, no rollover; 1 free secondary org

API included
Plan details

additional AI credits available for purchase (price not published on the pricing page)

Scale

$149/mo

billed monthly

$139/mo

billed annually

2,000 AI credits per user/month, shared pool up to 20,000/month, no rollover; unlimited call recording retention; custom roles; 1 free secondary org

API included
Plan details

additional AI credits available for purchase (price not published on the pricing page)

Rate limits

Per endpoint group (path + method groups).

More on limitsLess

Per-organization limit is 3x the per-API-key limit (the docs' 20 RPS per key = 60 RPS per org is an example, not a published value). Every 429 carries the RateLimit header (limit, remaining, reset seconds) and Retry-After; the old x-rate-limit-* headers and body fields are documented as replaced. Some endpoints have stricter, unpredictable limits. Live unauthenticated probe of GET /api/v1/me/ (2026-10-25) returned 'ratelimit: limit=100; remaining=100; reset=1' plus ratelimit-* and x-ratelimit-limit '100, 100;w=1' headers, i.e. 100 requests per 1-second window on that group; authenticated per-key values are not published.

How to get an API key

Close uses Basic auth. The steps below follow Close's own docs.

  1. Create a Close account. API access starts on the Solo plan.
  2. Settings > Developer > API Keys (scoped to a user/organization pair)
  3. Send it with every request: header: Authorization: Basic base64('<api_key>:') (key as username, empty password); OAuth 2.0 bearer for apps; MCP also accepts headers Close-API-Key + Close-Scope.
  4. Make a first call: Create a lead (company) with nested contacts, addresses, custom fields. Keep the key in an environment variable, never in the command.
    curl -X POST "https://api.close.com/api/v1/lead/" \
      -u "$CLOSE_API_KEY:" \
      -H "Content-Type: application/json" \
      -d '{}'

Where the docs live

WhatWhere
Documentationdeveloper.close.com
API referencedeveloper.close.com/api/overview
OpenAPI specdeveloper.close.com/openapi.json
llms.txtdeveloper.close.com/llms.txt
Changelogdeveloper.close.com/api/overview/changelog
Base URLhttps://api.close.com/api/v1
MCP serverhttps://mcp.close.com/mcp
SDKsPython: closeio/closeio-api (officially maintained by Close), Node.js: closeio/closeio-node (Close's GitHub org), Community: Ruby, PHP (incl. Laravel), C#/.NET, Elixir, Go

Strengths and limits

Where it fits

  • Inside-sales teams that call and email from the CRM
  • Change-data sync via the event log (30 days back) and filtered webhooks
  • Agent access via the remote MCP with read / write_safe / write_destructive scopes
  • Bulk edits/emails/sequences over a saved search (Smart View or Advanced Filtering query)

Where it falls short

  • Account-based models: Close's top object is the Lead (a company) with contacts nested inside
  • Free usage: every plan is paid; 14-day free trial, no card, but signup requires a phone number and consent to calls/texts
  • Batch record creation: no batch create endpoint in the docs; bulk actions operate on existing leads

Worth knowing

2 moreShow fewer

Who should use it

Use Close for
Inside-sales teams that call and email from the CRM
Look elsewhere for
Account-based models: Close's top object is the Lead (a company) with contacts nested inside

If Close is not the answer

Other CRM tools in this directory, each with its own review.

Before you build

Four things to settle first, each read off Close's own pages.

  • Confirm the API is on your planAPI access starts on the Solo plan. Free tier: No free plan.
  • Keep the key out of your codeBasic auth. It is sent as: header: Authorization: Basic base64('<api_key>:') (key as username, empty password); OAuth 2.0 bearer for apps; MCP also accepts headers Close-API-Key + Close-Scope.
  • Design around the rate limitPer endpoint group (path + method groups).
  • Know the catch before you scaleRate limits are per endpoint group and per key, with the org cap at 3x a single key; per-key numbers are not published (an unauthenticated probe showed 100 per 1-second window on GET /me/), so read the RateLimit header and honour Retry-After on 429. Source: developer.close.com/api/overview/rate-limits

Want us to build it for you?

Tell us what you want Close to do in your stack. We will show you how we would wire it into your data, outbound or CRM, and what we would check first.

Read from close.com/pricing, developer.close.com/api/overview and developer.close.com/api/overview/rate-limits. Verified 25 Oct 2026.

All 12 endpointsFor developers: method, path, what it does and what it costs.

Base URL: https://api.close.com/api/v1

Bulk and async: Bulk actions (edit, delete, email, sequence subscription) over a query or Smart View; async exports. Source: developer.close.com/api/resources/bulk-actions

Webhooks: Yes. POST /webhook/ with url + events[{object_type, action, extra_filter}]; response includes signature_key, payloads signed with HMAC-SHA256 in the close-sig-hash header. Failed deliveries retried with exponential backoff (up to every 20 min) for up to 72 hours; subscription auto-paused (queue cleared) if all deliveries fail for 3 days or the max queue length is reached, admins are emailed, and it must be re-activated via API. Source: developer.close.com/api/resources/webhooks (verified 2026-10-25)

12 endpoints
MethodPathWhat it doesCost
POST/lead/Create a lead (company) with nested contacts, addresses, custom fieldsnone
POST/lead/merge/Merge two leadsnone
POST/contact/Create a contact (lead_id optional since 2025-02-14)none
POST/data/search/Advanced Filtering: find leads or contacts matching arbitrary criteria (dedupe lookups)none
POSTasync/bulk_action/edit/Bulk edit every lead matching a query or Smart View (set status, custom field, etc.)none
POSTasync/bulk_action/delete/Bulk delete every lead (or object) matching a querynone
POSTasync/bulk_action/email/Send a bulk email (template) to every lead matching a querynone
POSTasync/bulk_action/sequence_subscription/Subscribe/pause/resume every matching contact in a sequencenone
POSTasync/export/lead/Export leads/contacts/opportunities to a filenone
GET/event/Event log of object changes, up to 30 days backnone
POST/webhook/Subscribe a URL to events with optional JSON filtersnone
POST/enrich_field/AI Field Enrichment: fill a custom field on a lead/contact (synchronous; may time out on complex guidance)docs: 'may consume credits or incur costs' (amount not stated); pricing: AI features draw on plan AI credits (500-2,000 per user/month, no rollover); MCP get_ai_credit_usage reports AI credit use per feature