Skip to Content
Developer docsBeta

Rate limits & pacing

How fast you can call the API, and how fast Mawgood sends.

Two different things control speed: how often you call the API (rate limits), and how fast Mawgood sends messages (pacing).

Rate limits

Each key can make 600 requests a minute. Over that, the API answers 429 with error.code: "rate_limited" and a Retry-After header (seconds). Wait that long, then retry with exponential backoff (for example 1 s, 2 s, 4 s… with a little random jitter), keeping the same Idempotency-Key on POST /campaigns.

You rarely need many requests: one POST /campaigns carries up to 10,000 recipients, and webhooks replace polling. If you read campaigns in a loop, switch to webhooks.

Pacing

WhatsApp limits how many people each number can message, and watches how customers react. Sending a large list all at once can lower your number's quality rating. So a campaign over your workspace's all-at-once limit goes out steady, over the fewest hours its hourly limit allows.

You can set it yourself with pacing in POST /campaigns: { "mode": "all_at_once" } or { "mode": "steady", "overHours": 6 } (1 to 336 hours). A pacing faster than your limit allows is raised to the minimum. When even 336 hours is too fast, the request fails with 422 split_required: split the list. The create response tells you what was used:

FieldMeaning
pacing.modeall_at_once: as fast as the number allows. steady: spread over time.
pacing.overHoursWith steady, about how many hours the send will take.
pacingAdjustedtrue when Mawgood picked or raised the pacing to fit your all-at-once limit.

Pacing works per number, so splitting one list into several campaigns from the same number doesn't send it faster. Marketing templates also wait out quiet hours, which can make a send take longer than overHours.

GET /numbers shows each number's qualityRating and messagingLimit from Meta.

On this page