Customer.io · Rate Limits

Customerio Rate Limits

Customer.io applies per-endpoint rate limits that differ by API surface. The Track (Behavioral Tracking) API has a fair-use limit of 100 requests per second for both live integrations and historical backfill, applying to v1 and v2. On the App API most requests are limited to 10 requests per second, with API-triggered broadcasts limited to 1 request every 10 seconds and transactional messages allowed up to 100 requests per second. The Pipelines / CDP API enforces payload-size limits of 64 KB per single request and 1 MB per batch request.

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

It captures 6 rate-limit definitions, measuring requests and bytes.

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

Tagged areas include Customer Messaging, Marketing Automation, Email, CDP, and Transactional.

6 Limits Throttle: 429
Customer MessagingMarketing AutomationEmailCDPTransactionalRate LimitingQuotasThrottling

Limits

Track API (Behavioral Tracking) account
requests
100/second
Fair-use limit for live integrations and historical backfill; applies to v1 and v2.
App API (general) account
requests
10/second
Default limit for most App API endpoints.
App API (API-triggered broadcast) account
requests
1 per 10 seconds
Broadcast trigger endpoint is heavily throttled.
App API (Transactional) account
requests
100/second
Transactional email/push/sms/in-app send endpoints.
Pipelines API (single request) request
bytes
64 KB
Maximum size of a single identify/track/page/screen/group/alias call.
Pipelines API (batch request) request
bytes
1 MB
Maximum size of a batch request.

Policies

Per-Endpoint Limits
Limits are enforced per endpoint category rather than a single global account limit.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on HTTP 429 responses.

Sources