WhatsApp API Rate Limits | Throughput and Troubleshooting

WhatsApp Business API has two separate limits, and confusing them is the most common cause of failed campaigns. Throughput is how fast one business phone number can send: 80 messages per second by default on Cloud API, upgradable to 1,000. Messaging limits are how many unique users your business portfolio can start conversations with in a rolling 24 hours, using template messages: from 250 for a new portfolio up to unlimited. Throughput errors clear in seconds if you slow down. Messaging limits clear only when the 24-hour window rolls over or your limit goes up.

This guide follows Meta's current developer documentation (see Official References below). Use it alongside our WhatsApp API documentation when planning campaign volume.

Throughput vs Messaging Limits

	Throughput	Messaging limit	Pair rate limit
What it limits	Messages per second	Unique users reached with template messages, outside a customer service window, in a rolling 24 hours	Messages to the same user
Applies to	Each business phone number	Whole business portfolio, shared by all its numbers	Each number and recipient pair
Default	80 msg/sec (20 msg/sec for numbers also using the WhatsApp Business app)	250 unique users per 24 hours	About 1 message every 6 seconds
Maximum	1,000 msg/sec	Unlimited	Fixed
What counts	All messages: inbound and outbound, text, media, templates	Only business-initiated template messages to new unique users	All messages to that user
Error when exceeded	130429 (Rate limit hit)	Sends beyond your limit fail, so check your limit in WhatsApp Manager	131056 (Pair rate limit hit)
Fix	Slow down, queue, retry with backoff	Wait for the window, or raise your limit	Wait before messaging that user again. Other users are unaffected
How it increases	Automatic upgrade (see below)	Verification, then automatic scaling	Does not increase

Two points to note:

• Replies inside a customer service window do not count towards your messaging limit. When a customer messages you first, your replies within 24 hours are not counted, so high support volume does not use up your limit. They still count towards throughput.
• Adding phone numbers does not add messaging capacity. Since Meta moved limits to the business portfolio level, every number in the portfolio shares one limit. Extra numbers do add throughput, because throughput is per number.

Messaging Limits- How They Scale

Messaging limit	Unique users per rolling 24 hours	How to reach it
Starting	250	Every new business portfolio starts here
2,000	2,000	Verify your business (yourself or through a partner), or send 2,000 delivered high-quality template messages to unique users, outside customer service windows, within a 30-day period
10,000	10,000	Automatic scaling
100,000	1,00,000	Automatic scaling
Unlimited	No cap	Automatic scaling

Automatic scaling: Above 2,000, Meta raises your limit one level within about 6 hours if you have used at least half your current limit in the last 7 days and your messages and templates have high quality ratings across all numbers. If you never use half your limit, it will not increase, however good your quality is.

To check your current limit through the API, read the whatsapp_business_manager_messaging_limit field. The older messaging_limit_tier field is deprecated.

Throughput- How It Scales

Each Cloud API phone number starts at 80 messages per second, counting inbound and outbound messages of all types. Meta upgrades a number to 1,000 messages per second automatically when all three of these are true:

1. The business portfolio has an unlimited messaging limit
2. The number has sent to at least 1,00,000 unique recipients in a 24-hour period
3. The number's quality rating is Medium (yellow) or higher

Numbers also used with the WhatsApp Business app are fixed at 20 messages per second.

Quality Rating- What Affects Your Limits

Quality ratings decide whether your messaging limit scales, and a low rating can stop scaling or lead to template and number restrictions. Meta bases them on recent customer feedback, mainly blocks and reports. Internally, we use these targets for our clients' campaigns. They are not Meta's thresholds:

Signal	Healthy	Warning
Customer block rate	Under 0.5% of recipients	Over 2%
Opt-out rate	Under 1% per campaign	Over 5%
Message read rate	Above 60%	Below 20%
Spam reports	Minimal	Any noticeable rise

Handling Throughput in Code

Pace sends with a rate limiter, not just concurrency. A queue that processes 80 jobs in parallel can still send far more than 80 messages per second.

const Queue = require('bull');

// Stay under the default 80 msg/sec per phone number
const messageQueue = new Queue('whatsapp-messages', {
  limiter: { max: 80, duration: 1000 }
});

async function queueMessage(to, template, vars) {
  await messageQueue.add({ to, template, vars }, {
    attempts: 5,
    backoff: { type: 'exponential', delay: 2000 }
  });
}

messageQueue.process(async (job) => {
  const { to, template, vars } = job.data;
  try {
    await sendWhatsApp(to, template, vars);
  } catch (err) {
    const code = err.response?.data?.error?.code;
    if (code === 130429) {
      // Throughput exceeded: throw so Bull retries with exponential backoff
      throw new Error('Throughput limit hit- retrying with backoff');
    }
    if (code === 131056) {
      // Pair rate limit: only this recipient needs to wait
      await messageQueue.add(job.data, { delay: 6000 });
      return;
    }
    throw err;
  }
});

Remember that the 80 msg/sec budget includes inbound messages. If you also receive heavy inbound traffic on the same number, set the limiter lower.

Troubleshooting Sequence

When sends start failing, work through these steps in order. Each step rules out one limit before you move to the next.

1. Read the exact error code from the API response or the statuses webhook. Do not rely on the HTTP status alone, because different limits can return similar HTTP responses.
2. Error 130429 → throughput. Look at your peak send rate per phone number for the failing period. If it was above 80 msg/sec (or 20 for numbers shared with the Business app), add a rate limiter as shown above and retry with exponential backoff. Remember that inbound messages count too.
3. Error 131056 → pair rate limit. Look for loops or duplicate jobs sending to the same user more than once every 6 seconds. Remove duplicates from your queue and delay that recipient only.
4. Sends fail after many successes in one day → messaging limit. Count the unique users you have reached with templates, outside customer service windows, in the last 24 hours, across all numbers in the business portfolio. Compare this with whatsapp_business_manager_messaging_limit or the limit shown in WhatsApp Manager. If you are at the limit, retrying will not help. Hold the rest of the campaign until the window rolls over.
5. Error 131049 (healthy ecosystem engagement) → per-user marketing limit. Meta is limiting how many marketing messages that user receives. Do not retry right away. Lower your marketing frequency to that segment.
6. Check quality ratings for the phone number and each template in WhatsApp Manager. A low rating stops your limit from scaling and can restrict templates, which explains why a limit you expected to rise has not.
7. Check the WhatsApp Business Platform status page. If errors began suddenly across all numbers with no change on your side, look for an incident before changing your code.
8. Confirm the fix with a small test. Send a few hundred messages at your new pace, check that the error rate is zero in the statuses webhook, then raise volume gradually.

For the full error list, see our WhatsApp API error codes reference.

Warm-Up Strategy- Scaling Messaging Limits Quickly

Automatic scaling needs you to use at least half your limit over 7 days, so steady, high-quality volume matters more than single large sends. This is the schedule we recommend for a verified portfolio starting at 2,000:

Stage	Daily unique users	Focus	Expected result
Days 1–7	1,000–2,000	Existing opted-in customers only. Your best-performing templates	Use over half the 2,000 limit and move to 10,000
Week 2	5,000–10,000	Expand to your full opted-in base while watching quality	Move to 100,000
Week 3+	50,000+	Full campaign volume with daily quality checks	Move to unlimited

If any template's quality drops to low, pause it and fix the content or targeting before scaling further.

Frequently Asked Questions- WhatsApp API Rate Limits

What happens when I hit the WhatsApp API rate limit? If you exceed your phone number's throughput, the Cloud API returns error 130429 until your send rate is back within your level. Slow down and retry with backoff. If you send to the same user too quickly, you get error 131056 for that recipient only. Reaching your messaging limit is different: retrying sooner will not help, and you have to wait for the rolling 24-hour window or a higher limit. Get Click Media's platform queues and paces sends automatically.

How do I increase my WhatsApp API messaging limit? New business portfolios start at 250 unique users per 24 hours. You reach 2,000 by verifying your business or by sending 2,000 high-quality template messages to unique users within 30 days. After that, Meta raises the limit one level at a time, within about 6 hours, whenever you have used at least half your current limit in the last 7 days and quality stays high.

Are OTP messages subject to the same rate limits? Yes. Authentication templates count towards the same throughput and messaging limits. For high OTP volume, Get Click Media offers a dedicated OTP queue with priority routing so OTPs are not stuck behind campaign sends.

Can I send unlimited messages on WhatsApp API? A portfolio on the unlimited messaging limit can reach any number of unique users, but throughput still applies per phone number: 80 messages per second by default, and up to 1,000 per second through Meta's automatic upgrade.

Official References

Rules last checked against Meta's documentation on 30 October 2026:

• Messaging limits- Meta for Developers
• Throughput- Meta for Developers
• WhatsApp Cloud API error codes- Meta for Developers
• WhatsApp Business Platform changelog
• WhatsApp Business Platform status page

Get Started

For related failure handling, see WhatsApp API error codes for the full error reference, and WhatsApp API documentation for high-volume sending.

Get WhatsApp Business API- Read API Docs · Get API Access · Talk to Technical Team