Attio · Rate Limits

Attio Com Rate Limits

Attio publishes explicit numeric rate limits for its REST API, expressed as requests per second split by operation type. Read requests are limited to 100 per second and write requests to 25 per second. Exceeding a limit returns an HTTP 429 (Too Many Requests) response, and clients are expected to back off and retry. Webhook delivery is separately capped at 25 requests per second per target URL, with support able to raise that on request.

Attio Com Rate Limits is the machine-readable rate-limit profile for Attio on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include CRM, API, Rate Limiting, Quotas, and Webhooks.

3 Limits Throttle: 429
CRMAPIRate LimitingQuotasWebhooks

Limits

Read Requests token
requests
100
Up to 100 read (GET and read-style query) requests per second per access token.
Write Requests token
requests
25
Up to 25 write (POST/PATCH/PUT/DELETE) requests per second per access token.
Webhook Delivery webhook
requests
25
Attio delivers at most 25 webhook HTTP POSTs per second to a given target URL; contact support to raise it.

Policies

Throttling Response
Requests over the limit receive an HTTP 429 (Too Many Requests) response.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and stay within the per-second read/write budgets.
Webhook Delivery Guarantee
Webhooks are delivered at-least-once with an Idempotency-Key header and a 5-second delivery timeout; consumers must deduplicate on the idempotency key.

Sources