Bird · Rate Limits

Bird Com Rate Limits

Bird enforces per-account request throttling on its platform APIs at api.bird.com, with additional per-channel throughput ceilings governed by carriers, Meta (WhatsApp), and number capabilities. The legacy MessageBird REST API at rest.messagebird.com documents explicit per-method limits (approximately 50 GET req/s and 500 POST req/s, with up to 50 recipients per message request). Platform per-account values are not fully reconciled here.

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

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

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

Tagged areas include CRM, Messaging, SMS, WhatsApp, and Email.

6 Limits Throttle: 429
CRMMessagingSMSWhatsAppEmailRate LimitingQuotasThrottling

Limits

Platform API Requests account
requests
see provider documentation
Per-account request throttling on api.bird.com endpoints.
Legacy GET Requests account
requests
~50 req/s
Documented for the legacy MessageBird REST API GET endpoints.
Legacy POST Requests account
requests
~500 req/s
Documented for the legacy MessageBird REST API POST endpoints.
Recipients Per Message request
recipients
50
Maximum recipients per legacy SMS message request.
WhatsApp Throughput channel
messages
governed by Meta messaging tier
WhatsApp send throughput is set by Meta's per-number messaging tier, not Bird alone.
SMS Throughput channel
messages
depends on number type and carrier
Long-code, short-code, and carrier capabilities determine per-second SMS throughput.

Policies

Tiered Limits
Throughput rises with plan tier, number provisioning, and channel warm-up (WhatsApp).
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources