Postmark Rate Limits
Postmark publishes NO numeric API rate limit and NO rate-limit response headers. It documents that a 429 exists and that you should slow down, and it documents hard payload/recipient caps that behave like limits. The only numeric throttle Postmark states anywhere is a self-policed SMTP connection recommendation.
Postmark Rate Limits is the machine-readable rate-limit profile for Postmark on the APIs.io network, in the API Commons Rate Limits shape.
It captures 11 rate-limit definitions, measuring messages_per_request, recipients_per_message, bytes_per_message, bytes_per_request, and bytes_per_field.
Limit state is signalled in the request, response, retryAfter, and rateLimitRemaining response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled, throttledTitle, throttledMeaning, and payloadTooLarge.
Tagged areas include Rate Limiting and Email.
requestresponseretryAfterrateLimitRemaining
Limits
Sources
- https://postmarkapp.com/developer/api/overview
- https://postmarkapp.com/support/article/do-we-have-rate-limits-for-smtp
- https://postmarkapp.com/llms.txt
- https://postmarkapp.com/pricing
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.