RudderStack · Rate Limits

Rudderstack Rate Limits

RudderStack publishes very little runtime rate-limit information. The HTTP tracking API documents a 429 "Too many requests" status but NO request-per-second cap, and the only numeric per-API rate limit anywhere in the documentation is on the User Suppression API, expressed as hourly token budgets. The real commercial constraint is the monthly event quota attached to the plan tier. Payload limits (32 KB per call, 4 MB per batch, 200-level JSON nesting) are documented and hard.

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

It captures 5 rate-limit definitions, measuring tokens, requests, and events.

The profile also includes response codes documented for throttled, payloadTooLarge, and badRequestOnOversize.

Tagged areas include Customer Data Platform, CDP, Event Streaming, Rate Limiting, and Quotas.

5 Limits Throttle: 429
Customer Data PlatformCDPEvent StreamingRate LimitingQuotasThrottling

Limits

User Suppression API — suppression tokens workspace
tokens · hour
4000
1 user = 1 token for a suppression request. Published verbatim by RudderStack as a table on the User Suppression API page.
User Suppression API — deletion tokens workspace
tokens · hour
200000
Token cost for deletion is users × destinations — m users across n destinations consumes m*n tokens. A 200-destination workspace exhausts the budget at 1,000 users per hour.
HTTP tracking API throttling source
requests
HONEST ZERO. RudderStack documents the 429 response but publishes no numeric request-rate cap for event ingest. Self-hosted rudder-server deployments inherit only the limits the operator configures.
Free plan monthly events workspace
events · month
250000
Growth plan monthly events (entry rung) workspace
events · month
1000000
Published volume ladder runs 1M / 3M / 5M / 7M / 10M / 25M, then sales-quoted. Enterprise volume is quoted.