Gupshup · Rate Limits

Gupshup Rate Limits

Gupshup does not publish a single fixed numeric request-rate limit for the messaging API. Throughput on WhatsApp is governed primarily by the underlying WhatsApp Business Platform: each business phone number has a Meta messaging tier (1K, 10K, 100K, or unlimited unique customers per rolling 24 hours) that increases automatically with quality and volume, and Meta enforces its own per-second throughput ceilings on template sends. Gupshup applies platform-level API throttling on top of that. Because messages are accepted asynchronously and correlated later via webhook events, senders should batch, respect HTTP 429 responses, and back off. Numeric per-account API limits are not documented as of the review date.

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

It captures 4 rate-limit definitions, measuring requests, unique_recipients, messages_per_second, and messages.

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

Tagged areas include Messaging, WhatsApp, CPaaS, Rate Limiting, and Quotas.

4 Limits Throttle: 429
MessagingWhatsAppCPaaSRate LimitingQuotas

Limits

Messaging API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the messaging API; platform throttling applies.
WhatsApp Messaging Tier phone_number
unique_recipients
1K / 10K / 100K / unlimited per 24h (Meta tier)
Business-initiated conversations are capped by the number's Meta messaging tier, which scales with quality and volume.
Template Send Throughput phone_number
messages_per_second
Meta-enforced (varies by tier)
Meta enforces per-second throughput ceilings on template message sends.
Inbound / Session Messages phone_number
messages
no fixed cap within the 24h service window
User-initiated session replies are not subject to the business-initiated tier cap.

Policies

Asynchronous Acceptance
Messages are accepted asynchronously (HTTP 2xx with a messageId); final delivery status arrives via webhook events (enqueued, sent, delivered, read, failed).
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Quality-Based Tiering
Meta raises or lowers a number's messaging tier based on message quality rating and volume; low quality can throttle or restrict sending.

Sources