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.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.