Plunk · Rate Limits

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.

Tagged areas include Email, Transactional Email, Marketing, Automation, and Open Source.

3 Limits Throttle: 429
EmailTransactional EmailMarketingAutomationOpen SourceSaaSRate LimitingQuotasThrottling

Limits

Requests Per Minute project
requests
~1000 per minute
Project-level API request rate limit on the hosted platform.
Email Sending Throttle project
emails
throttled per project
Outbound send rate is throttled per project to protect deliverability.
Bulk Operations project
jobs
automatically queued
Large campaign and bulk operations are queued rather than rejected.

Policies

Queuing
Bulk sends and high-volume operations are queued and processed asynchronously instead of being rejected.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor 429 responses.
Self-Hosted Configuration
Self-hosted deployments can configure their own rate limits and sending throughput.

Sources