Marketing API (cloudapi.mailercloud.com)
Requests are rate-limited per client IP using a sliding one-second window of 50 requests per second (higher limits can be arranged for specific IPs — contact support).
When the limit is exceeded the API responds:
The API does not currently send X-RateLimit-* or Retry-After headers. Clients — especially AI agents doing batch work — should treat any 429 as a signal to back off exponentially rather than expecting a server-provided retry time.
Email API (email-api.mailercloud.com)
Transactional sending is governed by your account’s sending quota and throttling rules rather than a fixed per-second number. Two internal status codes signal limits (see Errors):
Email Verifier API (verify.mailercloud.com)
Requests are rate-limited; a 503 service busy, please retry response also indicates transient capacity pressure — retry with backoff.
Recommended retry strategy
Retry 429, 5xx, and throttling responses with exponential backoff and jitter; do not retry validation (400) or auth (401/403) errors.
For sustained batch work (e.g. contact syncs), keep total request rate below the limit by pacing requests rather than relying on retries.