AhaSend · Rate Limits

Ahasend Rate Limits

AhaSend's published API rate limits and hourly sending limits, read from the rate-limits reference and the product changelog on 2026-08-30. This artifact REPLACES a 2026-05-04 scaffold whose per-tier request limits were invented defaults.

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

It captures 8 rate-limit definitions, across the pro, max, and legacy tiers, measuring requests_per_second, messages_per_hour, and composite.

Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.

Tagged areas include Email, Transactional Email, Rate Limiting, Quotas, and Throttling.

8 Limits Exhausted: HTTP 429 Quota: 429 limitremainingresetretryAfter
Transcribed from the provider's documentation on 2026-08-30 — ahasend.com/docs/api-reference/rate-limits.
View Source
EmailTransactional EmailRate LimitingQuotasThrottling

Limits

Standard API endpoints — sustained rate account
requests_per_second · second
100
Statistics endpoints — sustained rate account
requests_per_second · second
1
No burst allowance. These are the only operations whose 429 declares a Retry-After header.
Pro plan hourly sending — starting tier account
messages_per_hour · hour
1000
Steps up to 5,000 then 10,000 per hour as sending reputation and history build (July 2026 changelog).
Pro plan hourly sending — established tier account
messages_per_hour · hour
10000
Max plan hourly sending — starting tier account
messages_per_hour · hour
2000
Steps up to 20,000 then 100,000 per hour (July 2026 changelog).
Max plan hourly sending — established tier account
messages_per_hour · hour
100000
Legacy metered plans hourly sending account
messages_per_hour · hour
500
Legacy metered plans keep a 500 to 1,000 to 2,000 per hour curve.
SMTP relay per-message and per-connection limits connection
composite
Published in AhaSend's llms.txt and the SMTP server documentation; applies to send.ahasend.com and send-us.ahasend.com.

Policies

Backoff Strategy
AhaSend's documentation prescribes exponential backoff with jitter on a 429 and ships JavaScript and Python reference implementations on the rate-limits page.
Higher limits by review
Higher rate limits are available after a manual review; AhaSend directs high-volume senders to support@ahasend.com.
Prefer webhooks over polling
AhaSend explicitly recommends webhooks instead of polling, and caching for statistics, as the way to stay inside the 1 request/second statistics ceiling.

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/ahasend-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.