"Why did only part of my campaign go out?" is one of the most common questions from businesses new to the WhatsApp API, and the answer is rarely a fault. WappBlaster customers on the official WhatsApp Business Platform work within two separate ceilings that Meta sets: how many different people a business can message first in a rolling day, and how fast messages can be pushed through the API. Knowing which one you hit tells you what to fix, and in most cases the fix is patience and good quality rather than more spending.
Two WhatsApp API limits that people confuse
| Messaging limit | Throughput (rate) limit | |
|---|---|---|
| What it counts | Unique recipients of business-initiated templates in a rolling 24 hours | API requests or messages per second |
| Applies to replies? | No: replies inside the customer service window do not count | Yes, all sends share it |
| How it grows | Automatically in steps, when you use your current limit and quality stays healthy | Set by Meta per number; higher capacity comes with scale |
| What hitting it looks like | Messages to new recipients fail with a limit error until the window rolls | Requests are throttled or rejected for a short time |
Meta has adjusted the exact tiers and how they are counted more than once, so check the current limit shown in WhatsApp Manager for your account rather than relying on a figure from an old article.
Why a fresh number hits WhatsApp rate limits early
A number that has just been verified starts on a low messaging limit. An Indian coaching institute that imports 20,000 old enquiries and tries to message them all on day one will see most sends fail. The sensible approach is to start with your warmest contacts (recent enquiries, current students, recent buyers), send to a volume close to your current limit each day, and let the limit step up. Opted-in, engaged contacts help in two ways: they keep quality high, and they reply, which opens a customer service window, and your answers inside it do not count against the messaging limit at all. If a number arrives through migration from another provider, its history usually comes with it, so there is no reason to start from scratch.
Quality rating decides whether the WhatsApp API limit rises
The limit only climbs while quality is healthy. Blocks and reports from recipients pull quality down, and a number at low quality can be held at its current limit or moved down. WappBlaster's quality rating monitoring alerts you when the rating changes, which is the moment to pause marketing sends and look at which campaign caused it. The practical guidance in sending 1,000 messages a day safely applies at every scale.
Pacing requests within API rate limits when you build on WhatsApp
Businesses that call the REST API from their own code, for example to send order updates from an ERP, should pace their requests instead of firing a loop as fast as the server allows.
- Queue outgoing messages and release them at a steady rate.
- When a request is throttled, wait and retry with increasing delays rather than retrying instantly.
- Listen to the signed status webhooks for delivered and failed events, and log Meta's failure reason code for every failure.
- Separate limit errors from genuine failures such as invalid numbers, so you retry only what can succeed.
Before reporting an outage, check whether the failed requests were throttled during a burst; that is a pacing problem in your own code, and the fix above solves it.
Using more than one number
Large senders with separate brands, regions or departments can register several numbers and split traffic between them, for example one for transactional alerts and one for marketing. The multiple numbers setup lets each carry its own campaigns. This adds throughput capacity, but each number still needs its own good quality, and splitting one audience across numbers to dodge a limit only spreads the blocks around.
WhatsApp API rate limit fixes that make throughput worse
- Buying contact lists to "use up" a higher limit; unknown recipients block, quality falls, and the limit stops rising.
- Switching to unofficial senders when the official limit feels slow; those numbers get banned with no recourse.
- Sending the whole list at 9 am every time, which concentrates blocks and throttling into one burst. Scheduling by recipient timezone spreads international sends naturally.
WhatsApp API rate limits and what you pay
Your limits are set by Meta, not by a provider plan. WappBlaster's fee is the same ₹7999 per year (or $200 for international accounts) whatever your tier, and Meta's per-message charge for each delivered template is passed through at cost.