Leanplum · Rate Limits

Leanplum Rate Limits

Leanplum does not publish global per-minute numeric rate limits for its REST API. The one hard, documented constraint is on the multi (batching) method: a single multi call is limited to 50 users and/or 500 actions, and any call that exceeds this limit is ignored and returns HTTP 403. Each unique user lookup in a request counts as a separate billable API call, and concurrent requests touching the same users (from the SDK or API) are queued and executed after an in-flight multi batch completes. Beyond the multi limit, throughput is governed by account/contract terms rather than a public per-endpoint cap.

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 4 rate-limit definitions, measuring users, actions, characters, and requests.

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

Tagged areas include Mobile Marketing, Customer Engagement, Messaging, Rate Limiting, and Quotas.

4 Limits Throttle: 403
Mobile MarketingCustomer EngagementMessagingRate LimitingQuotas

Limits

Multi Batch - Users request
users
50
A single multi call may reference at most 50 users; exceeding this returns 403 and the call is ignored.
Multi Batch - Actions request
actions
500
A single multi call may contain at most 500 actions; exceeding this returns 403 and the call is ignored.
GET Request URL Length request
characters
2083
GET requests are bounded by a ~2,083 character URL limit; use POST for larger payloads.
Account Throughput account
requests
not published
No fixed numeric per-account request-rate limit is documented; throughput is governed by contract terms.

Policies

Billable User Lookups
Each unique user lookup in a request is counted as a billable API call, so batching users efficiently controls both throughput and cost.
Concurrent Request Queuing
While a multi batch is processing, concurrent requests for the same users (from SDK or API) are queued and executed after the batch completes.
Backoff Strategy
Clients should batch within the 50 user / 500 action limits and implement retry with exponential backoff on 403 responses.

Sources