Kaleyra · Rate Limits

Kaleyra Rate Limits

Kaleyra applies account-level throughput controls (API requests per second and per-channel send throughput/TPS) that are provisioned per account, plan, and region rather than published as a fixed public table. Downstream carrier, WhatsApp (Meta) messaging tiers, and India DLT scrubbing further govern effective throughput. Specific numeric limits are not published on the developer hub and are not reconciled in this artifact.

Kaleyra Rate Limits is the machine-readable rate-limit profile for Kaleyra on the APIs.io network, in the API Commons Rate Limits shape.

It captures 4 rate-limit definitions, measuring requests, messages, conversations, and concurrent_calls.

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 CPaaS, Messaging, SMS, WhatsApp, and Voice.

4 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-17.
Written by API Evangelist on 2026-07-17 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
CPaaSMessagingSMSWhatsAppVoiceRate LimitingThrottling

Limits

API Requests Per Second account
requests
see provider documentation
Provisioned per account/plan/region; not publicly tabled.
SMS Send Throughput (TPS) account
messages
see provider documentation
Effective SMS TPS depends on account tier and destination carrier.
WhatsApp Messaging Tier account
conversations
governed by Meta messaging tier
WhatsApp Business messaging limits (1K/10K/100K/unlimited) are set by Meta on the registered number.
Voice Concurrency account
concurrent_calls
see provider documentation
Concurrent outbound call channels provisioned per account.

Policies

Provisioned Limits
Throughput is set per account/plan/region and raised via account management.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on HTTP 429.

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/kaleyra-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.