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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-06-20.
Written by API Evangelist on 2026-06-20 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

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.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/respond-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.