Courier · Rate Limits

Courier Com Rate Limits

Courier applies per-endpoint rate limits on the REST API (base https://api.courier.com) and returns HTTP 429 when a limit is exceeded. Some configuration/management endpoints are rate limited more tightly than the high-throughput Send API. Courier's documentation calls out specific limits on a few endpoint families - for example Lists write operations and Events PUT at roughly 20 requests/minute, and Brands PUT at roughly 200 requests/minute - and enforces a maximum request body size of 6 MB across all endpoints (returning 413 Payload Too Large). Idempotency keys, supplied via the Idempotency-Key header, are honored for 24 hours to safely retry sends.

Courier Com Rate Limits is the machine-readable rate-limit profile for Courier on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring requests and bytes.

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

Tagged areas include Notifications, Messaging, Multi-Channel, Rate Limiting, and Quotas.

5 Limits Throttle: 429
NotificationsMessagingMulti-ChannelRate LimitingQuotas

Limits

Send API account
requests
high-throughput (not a documented fixed number)
The POST /send endpoint is built for volume; per-account throughput follows your plan rather than a small fixed cap.
Lists Write Operations account
requests
~20 per minute
POST/PUT operations on the Lists API are documented at roughly 20 requests/minute.
Events PUT account
requests
~20 per minute
PUT requests on the Events API are documented at roughly 20 requests/minute.
Brands PUT account
requests
~200 per minute
PUT requests on the Brands API are documented at roughly 200 requests/minute.
Request Body Size request
bytes
6 MB
All Courier API endpoints reject request bodies larger than 6 MB with 413 Payload Too Large.

Policies

Idempotency
Pass an Idempotency-Key header on send requests to safely retry without duplicate notifications; keys are honored for 24 hours.
Backoff Strategy
On a 429 response, back off exponentially with jitter and honor the Retry-After header before retrying.
Environment Scoping
API keys and limits are scoped per environment (test vs production); test traffic does not consume production allowances.

Sources