MailPace · Rate Limits

Mailpace Rate Limits

MailPace applies sending rate limits to protect deliverability when large volumes of email are sent over short periods. The send endpoint returns HTTP 429 Too Many Requests when limits are exceeded. Per-request structural limits also apply - a maximum of 50 recipients in the To field and a total message size of 50 MB. Specific numeric per-second/per-minute send rates are not published and are not reconciled in this artifact.

Mailpace Rate Limits is the machine-readable rate-limit profile for MailPace on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring emails, recipients, and bytes.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Email, Transactional Email, Messaging, SMTP, and Privacy.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-06-20.
Written by API Evangelist on 2026-06-20 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
EmailTransactional EmailMessagingSMTPPrivacyRate LimitingQuotasThrottling

Limits

Send Rate account
emails
see provider documentation
Sending too many emails over a short window returns HTTP 429.
Recipients Per Request request
recipients
50
Maximum of 50 addresses across the To field per send request.
Message Size request
bytes
52428800
Total email size, including attachments, may not exceed 50 MB.

Policies

Throttling Response
Exceeding the send rate returns HTTP 429 Too Many Requests.
Backoff Strategy
Clients should implement exponential backoff with jitter and retry queued sends.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/mailpace-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.