Rate Limits

The MailReach API does not currently enforce rate limits. We ask that you keep your traffic reasonable and build your integration so it can back off cleanly if the server is under pressure.

Recommended usage

As a guideline, stay under 20 requests per second per API key. This is a soft target, not an enforced ceiling. It keeps your integration comfortably inside the range we expect and ensures you won't be affected if we introduce hard limits in the future.

Handling errors

Status	Action
`5xx`	Retry with exponential backoff (see below)
`429`	Back off and respect the `Retry-After` header
`4xx`	Do not retry, fix the request

4xx errors indicate a problem with the request itself (bad parameters, missing authentication, unknown resource). Retrying an unchanged request will keep failing.

Exponential backoff

For 5xx responses, retry with increasing delays:

Attempt 1: wait 1s
Attempt 2: wait 2s
Attempt 3: wait 4s
Attempt 4: wait 8s
Give up after 4–5 attempts

Do not retry in a tight loop. It adds load without improving success chances. Cap retries at a few attempts and surface the failure to your application.

Tip

Implementing backoff today means your integration will handle 429 responses correctly the day limits are enforced, with no code changes needed.

Future limits

We reserve the right to introduce rate limits in the future. If we do:

We will announce it ahead of time in the changelog.
Rate-limited responses will use the standard 429 Too Many Requests status code.
They will include a Retry-After header indicating how long to wait before retrying.

Webhooks & Alerts