Emailoctopus Rate Limits
EmailOctopus publishes its v2 rate limit precisely. Verbatim from the API reference: "Requests to the API are subject to a rate limit, which is implemented using the token bucket algorithm. Each request consumes one token and your bucket holds up to 100 tokens. Tokens are replenished at a rate of 10 per second." That is a sustained 10 requests per second with a burst of 100. Exceeding it returns HTTP 429 (too-many-requests); the knowledge base adds that the connection is blocked "for up to a minute". Separately, plan-level subscriber and monthly-send caps apply and surface as a 422 out-of-limits error rather than a 429.
Emailoctopus Rate Limits is the machine-readable rate-limit profile for EmailOctopus on the APIs.io network, in the API Commons Rate Limits shape.
It captures 5 rate-limit definitions, measuring requests, emails, subscribers, and records.
Limit state is signalled in the X-RateLimiting-Remaining and X-RateLimit-Retry-After response headers, and an exhausted limit returns HTTP 429.
The profile also includes 5 backoff/retry policies defined and response codes documented for throttled and quota_exceeded.
Tagged areas include Email, Email Marketing, Newsletters, Campaigns, and Automation.
X-RateLimiting-RemainingX-RateLimit-Retry-After
Limits
Policies
Sources
- https://emailoctopus.com/api-documentation/v2
- https://help.emailoctopus.com/article/91-api-limits
- https://emailoctopus.com/pricing
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.