Respond.io · Rate Limits

Respond Rate Limits

The respond.io Developer API limits each API call method to 5 requests per second. When the limit is exceeded the API returns HTTP 429 (Too Many Requests) with a Retry-After header indicating how long to wait. Enterprise agreements can negotiate higher API limits. Per-channel messaging is additionally subject to the upstream channel provider's limits (for example WhatsApp Business Platform messaging tiers), which are not reconciled here.

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

It captures 3 rate-limit definitions, measuring requests and messages.

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

Tagged areas include Messaging, Omnichannel, Customer Conversations, WhatsApp, and AI.

3 Limits Throttle: 429
MessagingOmnichannelCustomer ConversationsWhatsAppAIRate LimitingQuotasThrottling

Limits

Requests Per Second (per method) method
requests
5
Each API call method is limited to 5 requests per second.
Channel Messaging Limits channel
messages
see channel provider documentation
Outbound messaging is also bounded by the connected channel provider's limits (e.g. WhatsApp messaging tiers, Messenger policies).
Enterprise API Limits account
requests
negotiated
Enterprise plans can negotiate higher API limits.

Policies

Retry-After Header
On 429 responses the API returns a Retry-After header; clients should wait the indicated duration before retrying.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After.

Sources