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, conforming to the API Commons Rate Limits specification.

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

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 Throttle: 429
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