> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sixtyfour.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Rate Limits

> Check request and concurrency limits and find out when to retry.

Limits apply per organization. Every API key and OAuth token in an organization, including keys used through the [MCP server](https://docs.sixtyfour.ai/developer-tools/mcp-setup.md), draws on the same budgets. A request over a rate limit returns `429` with a `Retry-After` header, and nothing runs.

## How limits are counted

| Kind | How it counts | A `429` carries |
| - | - | - |
| Per-minute limit | Requests in any 60-second window | `Retry-After` |
| Burst budget | Up to the burst at once, then a steady refill. 300 per minute with a burst of 15 allows 15 requests at once, then 5 a second | `Retry-After` and the `X-RateLimit-*` headers |

A request counts once Sixtyfour accepts it, even if it fails afterwards. Each endpoint has its own budget unless a table below says it shares one.

A `/v1` route has the same limit as the original route it replaces. The tables list both, with the `/v1` route first.

## Status polling

| Endpoint | Limit |
| - | - |
| [`GET /v1/jobs/{job_id}`](https://docs.sixtyfour.ai/api-reference/async-jobs), `GET /v1/jobs` and `GET /v1/jobs/{job_id}/items` | 300 per minute, burst 15 |
| [`GET /job-status/{task_id}`](https://docs.sixtyfour.ai/api-reference/enrichment/job-status) and `GET /workflows/runs/{run_id}/live_status` | The same budget |

At one poll every 10 seconds, the budget covers 50 Jobs in flight, with the polls spread out rather than sent together.

For more work than that, receive results by webhook and poll only as a fallback: pass `webhook_url` when you start a Job, and add an `outgoing_webhook` block to Workflows. See [Outgoing Webhooks](https://docs.sixtyfour.ai/api-reference/webhooks/outgoing.md).

A `429` on a status read does not affect the Job; read again after `Retry-After`. [Async Jobs](https://docs.sixtyfour.ai/api-reference/async-jobs.md#polling) has a polling helper.

## Limits by endpoint

### Files

| Endpoint | Limit | Notes |
| - | - | - |
| `POST /v1/files` | 20 per minute per organization | Ticket creation, finalization and multipart uploads share this budget |

File download URLs use the existing file-download budget. Two uploads can run concurrently per organization. Multipart uploads accept up to 45 MiB; direct upload tickets accept up to 100,000,000 bytes and 100,000 data rows.

### Jobs and exports

`POST /v1/exports` allows 20 requests per minute per organization, including replays, and two simultaneous submissions. Export rendering continues asynchronously after submission.

### Intelligence and contact

| Endpoint | Limit | Notes |
| - | - | - |
| `POST /bulk-intelligence/people`, `POST /bulk-intelligence/company` | 10 per minute each | A replay with the same `Idempotency-Key` does not count |
| `POST /verify-email` | 120 per minute | |
| `GET /v1/balance`, `GET /check-balance` | 60 per minute | |

### Workflows

| Endpoint | Limit | Notes |
| - | - | - |
| `POST /v1/workflows/{workflow_id}/runs`, `POST /workflows/run` | 120 per minute | A retry with the same `Idempotency-Key` that returns the run it already started does not count |
| `GET /workflows/runs/{run_id}/results/download-links` | 5 per second, burst 15 | Burst budget. A refused link request does not affect the run or its results; retry it instead of starting a new run. Each `download_url` lasts 15 minutes and draws on the file-download budget, not this one. See [Workflow result download retries](https://docs.sixtyfour.ai/api-reference/legacy/errors.md#workflow-result-download-retries) |
| Downloading a file from a `download_url` | 60 per minute, burst 5 | Burst budget, shared by workflow result links, webhook result links, and `GET /search/download` links |
| `GET /v1/templates` and `GET /v1/templates/{template_id}` without credentials, `GET /templates`, `GET /templates/{template_key}` | 120 per minute | The list and single-template routes share a budget, counted per IP address without credentials |
| `GET /v1/templates` and `GET /v1/templates/{template_id}` with credentials, `GET /templates/available` | 120 per minute | These routes share a budget, separate from the one above |

### Search

| Endpoint | Limit | Notes |
| - | - | - |
| `POST /v1/people/search`, `POST /v1/companies/search` | 200 per minute | |
| `POST /search/start-deep-search` | 200 per minute | Also 5 running at a time. See [Concurrency limits](#concurrency-limits) |
| `POST /search/query` | 200 per minute | |
| `POST /search/start-filter-search` | 200 per minute | Deprecated; use `POST /search/query` |
| `POST /search/filter-field-values` | 200 per minute | |
| `GET /search/filter-capabilities` | 300 per minute | |
| `POST /search/lookalike` | 200 per minute | `GET /search/lookalike/{task_id}` is not limited |
| `POST /search/export` | 10 per minute | |

### Monitors

| Endpoint | Limit | Notes |
| - | - | - |
| `POST /v1/monitors/upload`, `POST /monitors/upload` | 10 per minute | Replays count |
| `POST /v1/monitors/{monitor_id}/snapshots/export`, `POST /monitors/{monitor_id}/history-export` | 300 per minute, burst 15 | Burst budget. Also 5 builds at a time. See [Concurrency limits](#concurrency-limits) |

### Atlas

| Endpoint | Limit | Notes |
| - | - | - |
| `/v1/atlas/*` | 120 per minute | One budget across every Atlas endpoint. Each connection and reconnection to the event stream counts |

### Webhooks

| Endpoint | Limit | Notes |
| - | - | - |
| `POST /v1/webhooks/test-events`, `POST /webhooks/test-events` | 10 per minute | |

### Feedback

| Endpoint | Limit | Notes |
| - | - | - |
| `/v1/feedback`, `/v1/feedback/{feedback_id}`, `/feedback` and `/feedback/{feedback_id}` | 120 per minute, burst 20 | Burst budget. One budget across the Feedback endpoints |

### Team skills

| Endpoint | Limit | Notes |
| - | - | - |
| `/v1/skills`, `/v1/skills/{name}`, `/skills` and `/skills/{name}` | 60 per minute per API key | One budget across the Team skills endpoints |

### Connections

| Endpoint | Limit | Notes |
| - | - | - |
| `/v1/connections`, `/v1/connections/{name}`, `/connections` and `/connections/{name}` | 60 per minute per API key, signed-in person or OAuth client | One budget across the Connections endpoints. An OAuth token signed in as a person shares that person's budget |

### Media

| Endpoint | Limit | Notes |
| - | - | - |
| `GET /v1/media/{token}` | 600 per minute per IP address | |
| `GET /v1/media/profiles/{key}` | 600 per minute per IP address | Separate budget |

### OAuth tokens

`POST /oauth/token` issues up to 60 tokens per minute per client. Requests that fail client authentication are also limited to 25 per minute per client and to 120 per minute shared with other callers. Reuse each token until shortly before its `expires_in`. See [Using OAuth Clients](https://docs.sixtyfour.ai/guides/oauth-clients.md).

## Concurrency limits

### Deep search

Each organization runs up to 5 deep searches at a time, people and company combined. A start above that is never refused with `429`. It returns `200` with `status: "running"`, and the search then ends `failed` with this `error`:

```text theme={null}
Concurrency limit reached: max 5 concurrent deep_search requests. Please wait for an existing request to complete.
```

Start a new deep search only after one of yours reaches a final status.

### History exports

Each organization runs up to 5 history-export builds at a time. A sixth returns `429` with `Retry-After: 5` and the `detail` `Five history exports are already building for this organization. Retry later.`

## Response headers

| Header | Sent on | Meaning |
| - | - | - |
| `Retry-After` | Every `429`, and `503` responses you can retry | Seconds to wait before retrying |
| `X-RateLimit-Requests` | `429` from a burst budget | Requests added per period |
| `X-RateLimit-Period` | `429` from a burst budget | The period, in seconds |
| `X-RateLimit-Burst` | `429` from a burst budget | Requests available at once after idling |

Successful responses carry no `X-RateLimit-*` headers.

A `429` from the status polling budget:

```http theme={null}
HTTP/1.1 429 Too Many Requests
Retry-After: 1
X-RateLimit-Requests: 300
X-RateLimit-Period: 60
X-RateLimit-Burst: 15
Content-Type: application/json

{"detail": "Rate limit exceeded: 300 requests per minute per organization, with bursts of up to 15. Retry after the delay in Retry-After. Do not restart the job.", "error_code": "rate_limited", "request_id": "enrich_3f8b2c1e-9d4a-4c1b-8e2f-6a7b5c4d3e21", "retryable": true, "param": null}
```

A `429` from a per-minute limit:

```json theme={null}
{
  "detail": "Rate limit exceeded: 120 requests per minute. Retry after 12 seconds.",
  "error_code": "rate_limited",
  "request_id": "enrich_3f8b2c1e-9d4a-4c1b-8e2f-6a7b5c4d3e21",
  "retryable": true,
  "param": null
}
```

The original routes return the same `detail` with `code` and `correlation_id` in place of `error_code` and `request_id`.

## Retry after a 429

* Wait at least `Retry-After` seconds, then send the same request again.
* Workers that share an organization share its budgets. Coordinate them, and add a small random delay after the server's minimum.
* Stop after a bounded number of attempts.
* For many records, upload a file and start one Job, or use [Workflows](https://docs.sixtyfour.ai/api-reference/workflows/workflows-overview.md), instead of sending one request per record.

This helper retries `429` and `503` responses after `Retry-After`:

```python theme={null}
import time
import requests

def post_with_retry(url, headers, data, max_retries=5):
    for attempt in range(max_retries):
        response = requests.post(url, headers=headers, json=data)
        if response.status_code in (429, 503):
            time.sleep(int(response.headers.get("Retry-After", 2 ** attempt)))
            continue
        response.raise_for_status()
        return response.json()
    raise Exception("Max retries exceeded")
```

Contact [support@sixtyfour.ai](mailto:support@sixtyfour.ai) if a limit blocks your integration. For other status codes, see [Handling Errors](https://docs.sixtyfour.ai/api-reference/errors.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.