Leanplum Rate Limits
Leanplum publishes no global per-minute request cap and no rate-limit response headers, but it does publish four hard, numeric constraints: a 1 request/second per-device cap on development-mode traffic, a concurrency limit of one in-flight request per userId ("strict device locking"), the multi batching limits of 50 users / 500 actions per call, and a data-export quota of 24 exports per day. The only runtime throttling signal is the status code (429 for the rate and concurrency limits, 403 for an oversized multi) plus a message string inside response[].error.message — a client cannot read remaining quota anywhere.
Leanplum Rate Limits is the machine-readable rate-limit profile for Leanplum on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 10 rate-limit definitions, measuring requests, concurrent requests, users, actions, and exports.
The profile also includes 4 backoff/retry policies defined and response codes documented for throttled and batch_exceeded.
Tagged areas include Mobile Marketing, Customer Engagement, Messaging, Rate Limiting, and Quotas.
Limits
Policies
Sources
- https://docs.leanplum.com/reference/responses
- https://docs.leanplum.com/reference/batching-requests
- https://docs.leanplum.com/reference/reduce-billable-requests
- https://docs.leanplum.com/reference/making-requests
- https://docs.leanplum.com/reference/get_api-action-exportdata
- https://docs.leanplum.com/reference/post_api-action-addpostback
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.