MailerLite · Rate Limits
Mailerlite Rate Limits
MailerLite enforces a global 120 requests-per-minute limit per account, plus a separate 5 requests-per-minute limit on import-creation endpoints. Exhaustion returns HTTP 429 with Retry-After.
Mailerlite Rate Limits is the machine-readable rate-limit profile for MailerLite on the APIs.io network, in the API Commons Rate Limits shape.
It captures 2 rate-limit definitions, measuring requests.
An exhausted limit returns HTTP 429.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and validation.
Tagged areas include Email Marketing, Rate Limiting, Quotas, and Throttling.
2 Limits
Exhausted: HTTP 429
Transcribed from the provider's documentation on 2026-08-13 — developers.mailerlite.com/getting-started.
View Source
Email MarketingRate LimitingQuotasThrottling
Limits
Global API requests account
120/1 minute
Import creation account
5/1 minute
This limit is IN ADDITION to the global 120/min budget, has its own distinct 429 message, and — critically — is triggered implicitly: a batch composed entirely of subscriber upserts is silently reclassified as a bulk import and charged against it. A client batching upserts to stay under the global limit walks straight into this one.
Policies
Honour Retry-After
Both 429 variants publish Retry-After; use it rather than a fixed sleep. Documented example values are 119s (global) and 60s (import).
Backoff strategy
MailerLite explicitly recommends "batch endpoint and/or implement backoff strategy that would even out the requests over time".
Version pinning
Pin the API version with the X-Version header for predictable behavior.
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.