Skip to main content
To protect service availability and maintain optimal sending queues, Mailofly applies rate limits across API endpoints.

Default Rate Limits

When a rate limit is exceeded, the API returns an HTTP 429 Too Many Requests status code with a Retry-After header indicating seconds to wait.

Rate Limit Categories

Rate limits are evaluated using a sliding window per API key (or client IP for unauthenticated calls):
  • Sending Burst: Applies to high-frequency email dispatching endpoints including POST /emails, POST /emails/batch, and POST /campaigns/:id/send.
  • Read / List Endpoints: Applies to all retrieval operations (GET /*).
  • Other Mutations: Applies to resource creation, updates, and deletions (POST, PATCH, DELETE).

Response Headers

Every response from the Mailofly API includes headers indicating your current rate limit status:

Rate Limit Exceeded Response

When your request rate exceeds the tier allowance, Mailofly responds with HTTP 429 Too Many Requests: