Customer Io 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.
Customer Io 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.
Limits
Policies
Sources
- https://docs.customer.io/integrations/api/track/
- https://docs.customer.io/integrations/api/app/
- https://docs.customer.io/integrations/api/cdp/
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/customer-io-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.