What we do
Tools
Industries
Department
How we workLet's talk →
Home/Close/Close API Code That Holds Up at Full Volume
Close CRM

Close API: The Key, the First Request and the Rules That Bite Later

The script ran fine against ten leads. Against the whole org it hit 429s, stopped short of the last page of results, and wrote yesterday's deal value from a webhook that arrived after a newer one. None of that is a bug in Close. They're documented rules of the Close API, and far easier to build for on day one than to retrofit.

Close API essentials

Docs: developer.close.com, with the full reference, a changelog, and client libraries for Python, Node.js, Ruby, PHP and Go.

Key: each API key belongs to one user in one organization.

Settings Developer API Keys

Auth: HTTP Basic, with the key as the user name and an empty password. Integrations that other Close users sign in to use OAuth 2.0 instead.

Base URL: https://api.close.com/api/v1. GET /me/ is the quickest way to prove a key works.

A first Close API request, then the next four you'll need

  1. 1

    Create a key for this integration alone

    Settings Developer API Keys

    Since a key is tied to a user and an organization, make it under the user the integration should act as, and give each integration its own key.

  2. 2

    Call /me/

    curl https://api.close.com/api/v1/me/ -u yourapikey: returns the user the key belongs to.

    Watch for: the colon after the key. It stands for the empty password, and leaving it off makes curl prompt for one.

  3. 3

    Page through leads

    List endpoints take _skip and _limit and return a data array with a has_more flag. Page 2 of 100 is /api/v1/lead/?_skip=100&_limit=100.

    Watch for: the maximum _skip, which varies by resource. For a full pull, split by date_created ranges or use the Export API. Advanced Filtering search and the event log page by cursor instead.

  4. 4

    Read the RateLimit header

    Most responses carry RateLimit: limit=…, remaining=…, reset=…. On a 429, wait the rate_reset seconds before calling that endpoint again. Close recommends it over retry-after because it's more precise.

    Watch for: limits are set per endpoint group, so reads and writes on the same path can sit in different groups and run out separately.

  5. 5

    Set up a webhook subscription

    Create a subscription through the API for the object types and actions you care about, such as opportunity updates. Store the signature_key from the create response: it's what every delivery will be signed with.

Before a Close integration runs on live data

  • Does every integration have its own key?

    Close limits each key below the organization's ceiling, which is three times the per-key rate. Three busy keys fit; a fourth can tip the whole org over and slow every other tool on it.

  • Is every webhook delivery checked against its signature?

    Each POST carries close-sig-hash and close-sig-timestamp. The hash is an HMAC SHA-256 of the timestamp and the payload, made with your signature_key. Recompute it and compare in constant time.

  • Does the receiver answer inside 15 seconds?

    Close wants a connection within 5 seconds and a 2xx within 15. Slower deliveries are retried with growing gaps, up to every 20 minutes for 72 hours. Queue the work and answer first.

  • Does it re-read the record instead of trusting the payload?

    Close doesn't guarantee event order. Fetch the opportunity or lead fresh when an event arrives, so a late delivery can't overwrite newer values.

  • Can you replay what was missed?

    The event log keeps 30 days. A subscription pauses after 3 days of failed deliveries, or when its backlog reaches 100,000 events, and only comes back when it's switched on through the API.

What Close's directory leaves to the API

Close's integration directory centers on the selling side: email, calendars, calling, meeting notes and lead data. Accounting, inventory and project tools aren't in it. Close integrations lists what connects natively and through Zapier.

Zapier copes with a plain trigger: a new lead creates a task somewhere else. It gets awkward when the logic is conditional, when volume climbs, or when the workflow has to check another system first, such as whether an account is current on its invoices before a rep calls. That's where code on the API and webhooks takes over.

Close also publishes an MCP server for AI agents, which lets an assistant read and work with Close data in a conversation. It's a different job from a sync: anything that moves money or records between systems still belongs in tested integration code.

Close API follow-ups

Does Close integrate with Zapier?

Yes. Zapier links Close to a long list of apps for simple trigger-based automations. It suits straightforward tasks, and struggles with conditional logic or high volume, where code on the API does better.

Does Close have a native accounting integration?

No. Close's integration directory doesn't list an accounting connector for QuickBooks, Xero or similar software. Moving deal data into accounting on its own means building it on the Close API and webhooks.

Can I import leads into Close from another CRM?

Yes, with a CSV import as part of switching. A larger move that keeps custom fields and history intact is closer to a small project than a one-click import, and the paging and rate rules above apply if it's scripted.

Does Close support webhooks?

Yes. Subscriptions are set up through the API for chosen object types and actions, deliveries are signed, and failed ones are retried for up to 72 hours. That saves an integration from polling for changes.

Who writes Close API integrations when Zapier runs out?

n-frames does, for sales teams whose won deals, billing status or product data need to move between Close and other systems, with the rate limits, signatures and replay handled from the start.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.