Whippy · Rate Limits

Whippy Rate Limits

The Whippy Public API enforces per-organization request rate limits and bounded page sizes on list endpoints (limit default 50, max 500), with per-request maximums on bulk operations such as adding contacts to a sequence (1-4000 contacts per call). Specific requests-per-minute / requests-per-second ceilings are governed per account and tier and are not reconciled in this artifact; messaging throughput is additionally bounded by each plan's monthly credit allocation and carrier throughput.

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

It captures 4 rate-limit definitions, measuring results, contacts, requests, and messages.

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

Tagged areas include Communication, Messaging, SMS, Email, and Campaigns.

4 Limits Throttle: 429
CommunicationMessagingSMSEmailCampaignsSequencesRate LimitingQuotasThrottling

Limits

List Page Size request
results
50 default / 500 max
limit query parameter on list endpoints; offset is used for pagination.
Sequence Contacts Per Request request
contacts
4000
The 'to' array on POST /sequences/{id}/contacts accepts 1-4000 contacts.
Requests Per Minute organization
requests
see provider documentation
Per-organization API request rate; varies by account and is not reconciled here.
Messaging Throughput organization
messages
bounded by plan credits and carrier
Outbound messaging is metered against the plan's monthly credit allocation and carrier limits.

Policies

Tiered Limits
Limits and credit allocations scale with the subscribed plan tier (Lite through Custom).
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources