warmup_limit — Warm-up ladder cap reached
What the API returns
{
"error": {
"code": "warmup_limit",
"message": "The warm-up limit for this channel is reached.",
"request_id": "req_01JRQ8F4X9N2K7YB3C5V6W8H0T"
}
}Every Wapito error is this one envelope. Branch on code, which is stable; message is written for people and can be reworded; details appears only when there is something specific to say; request_id is what to quote to support.
What it means
warmup_limit is an HTTP 429 error from the Wapito WhatsApp API: warm-up ladder cap reached. The response message reads “The warm-up limit for this channel is reached.” It is retryable: the same request can succeed later without changes. 5 endpoints can raise it, POST /messages/text among them.
Why it happens
A newly linked number is rationed for its first week. Wapito counts the days since the number connected and caps total sends per day on a ladder of 50, 100, 200, 350, 500, 750 and 1000, after which the plan's own ceiling takes over. The send that would have crossed today's rung is refused before it reaches WhatsApp and is not counted. details.day is the ladder day, details.cap the rung and details.used what has gone out so far today. A reconnect of the same number keeps its place on the ladder; linking a different number starts it again.
How to fix warmup_limit
Read details.cap and details.used and schedule the remainder of the batch for after midnight UTC, when the daily counter resets.
Spread a migration over the first week instead of moving all traffic on day one; the rungs are sized for a number that is growing, not one that is being switched on.
If the volume is steady production traffic, connect the number a week before go-live so the ladder is behind you when the real load arrives.
Endpoints that raise it
Where you will meet it
- Send Without Template
Feature guide
Retry guidance
Safe to retry
The condition is transient, so the same request can succeed later without any change on your side. Retry with exponential backoff and jitter — start at one second, double each attempt, cap at a minute — and stop after a handful of tries so a stuck condition surfaces as an alert rather than a hot loop.
On a 429, read the Retry-After header first when the response carries one — rate_limited always sends it, in seconds — and when the details object names a window or a reset time, wait for exactly that. Both beat a guessed backoff.
Frequently asked questions
Can a premium channel skip the warm-up ladder?
No. The ladder, the send spacing and the cold-send guard apply to every plan and are never bypassed, because they are what keeps a number alive through months of automation. A premium plan raises the ceiling you reach after the first week; it does not remove the week.
Does the ladder restart when I reconnect after a disconnect?
Not for the same number. The ladder is anchored to the phone number the channel is linked to, so scanning a new QR for the same number keeps the day you were on. Linking a different number is a new start, because WhatsApp's history for the old one does not carry over.
Related
Try it on your own number
Create a channel, link a WhatsApp number by QR or pairing code, and call the API in a couple of minutes. The Sandbox plan is free and needs no card.