Plunk Rate Limits
The Plunk hosted API enforces a project-level rate limit of approximately 1,000 requests per minute. Email sending is additionally throttled per project and bulk operations (such as large campaign sends) are automatically queued rather than rejected. Requests that exceed the limit return HTTP 429. Self-hosted deployments can configure their own limits.
Plunk Rate Limits is the machine-readable rate-limit profile for Plunk on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests, emails, and jobs.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, throttledCode, billingCapped, and billingCappedCodes.
Tagged areas include Email, Transactional Email, Marketing, Automation, and Open Source.
Limits
Policies
Sources
- https://docs.useplunk.com/api-reference/overview
- https://docs.useplunk.com/api-reference/errors
- https://docs.useplunk.com/concepts/billing
- https://www.useplunk.com/pricing
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/plunk-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.