---
title: "Close API: pricing, rate limits & MCP | ONEGTMLAB"
description: "Close API: Calling- and email-first sales CRM for SMB sales teams, with a lead-centric REST API v1 (OpenAPI since 2026-04), advanced filtering, bulk…"
canonical: https://www.onegtmlab.dev/tool-directory/crm/close
---

# Close API: pricing, rate limits & MCP | ONEGTMLAB

[](/)

[

Book a call

](/book)

![](/_astro/close.BGAid65p.svg)

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

[

See pricing

](#pricing)[

Close API docs

](https://developer.close.com/api/overview)

At a glance

Category

CRM

Pricing model

Per seat

Free tier

No free plan

Entry price

$9/mo, billed annually Solo

Auth

Basic auth

Official MCP

Yes

Best for

Inside-sales teams that call and email from the CRM

[close.com ↗](https://www.close.com)[Pricing page ↗](https://www.close.com/pricing)

## What a call costs

The actions you pay for, as Close prices them.

Action

Cost

Per

Call recording + transcription add-on

$50/month per org + $0.02

per minute

Phone lines (BYOL or rent)

from $1

per line/month

Calling and SMS

passed through at cost; most outbound calls ~ $0.02

per 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 includedPlan 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 includedPlan 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 includedPlan 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 includedPlan 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

What

Where

Documentation

[developer.close.com](https://developer.close.com/)

API reference

[developer.close.com/api/overview](https://developer.close.com/api/overview)

OpenAPI spec

[developer.close.com/openapi.json](https://developer.close.com/openapi.json)

llms.txt

[developer.close.com/llms.txt](https://developer.close.com/llms.txt)

Changelog

[developer.close.com/api/overview/changelog](https://developer.close.com/api/overview/changelog)

Base URL

`https://api.close.com/api/v1`

MCP server

`https://mcp.close.com/mcp`

SDKs

Python: 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

-   Rate 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](https://developer.close.com/api/overview/rate-limits)
-   API keys use HTTP Basic with the key as username and an EMPTY password (note the trailing colon). Source: [developer.close.com/api/overview/api-key-authentication](https://developer.close.com/api/overview/api-key-authentication)
-   Webhook subscriptions silently stop after 3 days of failed delivery (auto-paused) and need an API call to resume. Source: [developer.close.com/api/resources/webhooks](https://developer.close.com/api/resources/webhooks)
-   Event log only goes back 30 days. Source: [developer.close.com/api/resources/events](https://developer.close.com/api/resources/events)
-   Only the Python (closeio-api) and Node.js (closeio-node) clients come from Close; the Ruby, PHP, C#, Elixir and Go libraries are community-built. Source: [developer.close.com/api/overview/api-clients](https://developer.close.com/api/overview/api-clients)

2 moreShow fewer

-   The OpenAPI spec (since 2026-04-06) is marked experimental: Advanced Filtering POST /data/search/ is missing, and create-lead/merge/export bodies are untyped, so use the per-endpoint docs pages for request fields. Source: [developer.close.com/api/overview/changelog/2026/4/6](https://developer.close.com/api/overview/changelog/2026/4/6)
-   enrich\_field via MCP needs the mcp.write\_destructive scope, and the REST call is synchronous and may time out on complex guidance. Source: [developer.close.com/mcp/tools](https://developer.close.com/mcp/tools); [developer.close.com/api/resources/field-enrichment](https://developer.close.com/api/resources/field-enrichment)

## 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.

[

![](/_astro/attio.CoO4UDxn_Zx1tGp.webp)

Attio

CRM

Free planOfficial MCP

Best for start-ups and agencies wanting a free/cheap CRM with API, webhooks and MCP on every plan.

Attio API review →](/tool-directory/crm/attio)[

![](/_astro/copper.CFmJ3qY-.svg)

Copper

CRM

From $23/mo

Best for google Workspace teams that want a simple CRM inside Gmail.

Copper API review →](/tool-directory/crm/copper)[

![](/_astro/folk.B0kqszAJ_29Kdhq.webp)

folk

CRM

From $24/moOfficial MCP

Best for agencies, VCs and founder-led teams that want a simple CRM their agents can write to.

folk API review →](/tool-directory/crm/folk)

## Before you build

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

-   **Confirm the API is on your plan**API access starts on the Solo plan. Free tier: No free plan.
    
-   **Keep the key out of your code**Basic 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 limit**Per endpoint group (path + method groups).
    
-   **Know the catch before you scale**Rate 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](https://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.

[

Book a call

](/book)[

See case studies

](/case-studies)

Read from [close.com/pricing](https://www.close.com/pricing), [developer.close.com/api/overview](https://developer.close.com/api/overview) and [developer.close.com/api/overview/rate-limits](https://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](https://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](https://developer.close.com/api/resources/webhooks) (verified 2026-10-25)

Filter endpoints

12 endpoints

Method

Path

What it does

Cost

POST

`/lead/`

Create a lead (company) with nested contacts, addresses, custom fields

none

POST

`/lead/merge/`

Merge two leads

none

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 query

none

POSTasync

`/bulk_action/email/`

Send a bulk email (template) to every lead matching a query

none

POSTasync

`/bulk_action/sequence_subscription/`

Subscribe/pause/resume every matching contact in a sequence

none

POSTasync

`/export/lead/`

Export leads/contacts/opportunities to a file

none

GET

`/event/`

Event log of object changes, up to 30 days back

none

POST

`/webhook/`

Subscribe a URL to events with optional JSON filters

none

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

[](/)

© 2026 ONEGTMLAB Private Limited. All rights reserved.

COMPANY

[

Why Us

](/#why-us)[

Process

](/#timeline)[

Blogs

](/blogs)[

About

](/about)[

Clients

](/clients)[

Free resources

](/free-resources)[

Newsletter

](/newsletter)

Services

[

GTM Engineering

](/ai-gtm-engineering)[

Account-Based Marketing

](/services/account-based-marketing)[

Paid Media

](/services/paid-media)[

Content Engineering

](/linkedin-personal-branding)[

RevOps

](/services/revops)[

SEO, AEO & GEO

](/services/seo-aeo-geo)[

All services

](/services)

![](/_astro/wordmark-3d.CMEfGdYr.svg)
