Skip to Content

Rate limits

The Kenso API limits calls two ways: per workspace, by the kind of call, and per operation, for each API key. A call has to fit both.

Ken-Version: 2026-11-02
Markdown

The limits

Kenso limits API key calls per workspace: per minute by the kind of call, and per day for all calls together. The limits depend on your workspace's plan, and Kenso can set other limits for a workspace.

KindFreeStandardElevated
Read (GET), per minute6003,00012,000
Write (POST, PATCH, PUT, DELETE), per minute2401,2004,800
Bulk (bulk operations such as bulk-create, and imports), calls per minute24120480
Heavy (search, exports, analytics, AI runs), per minute1260240
Sensitive (API keys, members, billing, webhooks, integrations), per minute303030
All calls, per day200,0001,000,0004,000,000
Items sent to bulk operations, per day200,0001,000,0004,000,000

The Free plan is on Free, the Premium, Done-for-you and Performance plans are on Elevated, and every other plan on Standard.

Every response reports the rate limit the request is closest to reaching, whether that is your plan's limit, your API key's own limit or a limit on the operation: RateLimit-Limit (the limit), RateLimit-Remaining (the requests left) and RateLimit-Reset (the seconds until it resets). A 429 from one of these limits carries the same three headers, with RateLimit-Remaining: 0, and Retry-After. Over your plan's limit, the response is 429 rate_limited, and its details names the class, limit and window you hit. A 429 quota_exceeded is a usage quota, not a rate limit: wait the Retry-After seconds. Spread bulk work over the day instead of sending it in bursts.

Responses to an API key also carry X-RateLimit-Remaining-Minute and X-RateLimit-Remaining-Day, your key's own counters. They are deprecated: read the RateLimit-* headers instead.

Each operation also has its own limit per API key, on top of the workspace limits, and some are much lower than the table. The operation's description states it, and its x-ken-rate-limit field gives it as limit calls per windowSeconds, with per saying what is counted: api_key, or ip on the few calls made without a key. Over an operation's own limit, the response is 429 rate_limited with the headers above, Retry-After and the error body.

Some operations also count each call against a quota that allows fewer calls than the operation's own limit, such as email finds. There, x-ken-rate-limit lists each such quota under quotas (its policy, what it counts per: workspace, user or ip, its limits per windowSeconds, and the plans whose limits differ) and states them in summary. Over a quota, the response is a 429 with Retry-After. Its code is quota_exceeded on most operations and rate_limited on some; each operation's Errors list names the code.

Each operation's own limit

Every operation's page in the reference shows its own limit under its endpoint: per API key, or per IP address on the few calls made without a key. Most are at least as high as the workspace limits, so the workspace limit is the one you meet first. Some operations that send, launch or start work are capped far lower.

These operations are capped under 100 calls a minute per API key, or per IP address where the table says so:

OperationEndpointCalls a minute
Start an enrichment runPOST /v1/campaigns/{campaignId}/enrichment-runs10
Launch a campaignPOST /v1/campaigns/{campaignId}/launch10
Retry failed enrichmentPOST /v1/campaigns/{campaignId}/retry-enrichment10
Start a CLI loginPOST /v1/cli/logins10 per IP address
Create a contact exportPOST /v1/contact-exports10
Start a domain health checkPOST /v1/domain-health-checks10
Check a domain's nameserversPOST /v1/domains/{domainId}/check-nameservers10
Verify a domain's tracking DNSPOST /v1/domains/{domainId}/verify-dns10
Import SMTP inboxesPOST /v1/inbox-imports10
Connect an SMTP inboxPOST /v1/inboxes10
Verify an inbox connectionPOST /v1/inboxes/{inboxId}/verify10
Start an inbox connect sessionPOST /v1/inboxes/connect-sessions10
Start a LinkedIn connect sessionPOST /v1/linkedin-accounts/connect-sessions10
Start a placement testPOST /v1/placement-tests10
Start an email threadPOST /v1/threads10
Forward an email threadPOST /v1/threads/{threadId}/forward10
Send a reply in a threadPOST /v1/threads/{threadId}/messages10
Start a hosted WhatsApp connect or reconnect sessionPOST /v1/whatsapp-accounts/connect-sessions10
Create a bug reportPOST /v1/bug-reports20
Add a note to a bug reportPOST /v1/bug-reports/{bugReportId}/notes20
Duplicate a campaignPOST /v1/campaigns/{campaignId}/duplicate20
Create an access requestPOST /v1/access-requests30
Connect a CRMPOST /v1/crm-connections30
Finish an OAuth connectionPOST /v1/crm-connections/oauth/complete30
Export job postingsPOST /v1/job-postings/search/export30
Share a saved list by emailPOST /v1/saved-lists/{savedListId}/invites30
Upload an image for a Facebook replyPOST /v1/threads/{threadId}/images30
Create your sandbox and its first test keyPOST /v1/sandboxes50
Reset your sandbox to its seed dataPOST /v1/sandboxes/{sandboxId}/reset50
Create another test key for your sandboxPOST /v1/sandboxes/{sandboxId}/test-keys50
Start an AI runPOST /v1/campaigns/{campaignId}/ai-runs60
Score a campaign's contactsPOST /v1/campaigns/{campaignId}/scoring/run60
Scan an import filePOST /v1/contact-imports/scans60
Regenerate a contact's AI linesPOST /v1/contacts/{contactId}/ai-lines/regenerate60
Rebuild the outbound sitePOST /v1/outbound-site/refresh60
Get an endpoint's signing secretGET /v1/webhook-endpoints/{webhookEndpointId}/signing-secret60
Rotate an endpoint's signing secretPOST /v1/webhook-endpoints/{webhookEndpointId}/signing-secret/rotate60

When you get a 429

  • Wait the Retry-After seconds, then send the request again.
  • No Retry-After header: wait a moment, and double the wait after each further 429.
  • A workspace limit answers with the code rate_limited. An operation's own limit, and the per-key and per-IP limits in front of the API, answer with a plain-text body or { "error": "Rate limit exceeded" } instead of the error object. Branch on the status, not on code.
  • Watch RateLimit-Remaining and slow down before it runs out.
  • Retrying a write is safe only with an Idempotency-Key: see Idempotency.

More guides

On this page