How to Send Bulk WhatsApp Messages via API (2026 Guide)
Any statistics or percentages in this article are general industry figures or illustrations, not QuackAPI measurements or promises. Results depend on your audience, consent and sending patterns. QuackAPI connects to WhatsApp as a linked device (an unofficial method), so read our risk and acceptable use policy before sending.
What Is Bulk WhatsApp Messaging?
Bulk WhatsApp messaging means sending a large number of messages — promotions, notifications, alerts, or updates — to many recipients in a short time. Unlike email blasts, WhatsApp messages have a 98% open rate and typically get read within 3 minutes.
However, WhatsApp actively monitors for spam behavior and will ban accounts that send bulk messages without following best practices. This guide covers how to send bulk messages safely and effectively using QuackAPI's REST API.
Before you start: read our WhatsApp API pricing guide to understand the cost structure, and our best practices guide for safe messaging.
Setting Up for Bulk Messaging
You need a QuackAPI account and at least one connected WhatsApp device. For high-volume bulk sends (10,000+ messages/day), use the Professional or Enterprise plan with multiple devices — spreading messages across 5 devices reduces the per-device rate and lowers ban risk.
Get your API key from your QuackAPI dashboard and note your device IDs. You will rotate messages across devices in your bulk send script.
import os
import time
import requests
API_KEY = os.environ["QUACKAPI_KEY"]
BASE_URL = "https://quackapi.com/v1/messages/send"
DEVICE_IDS = [1, 2, 3] # Your connected device IDs
headers = {
"Content-Type": "application/json",
"x-api-key": API_KEY
}Rate-Limited Bulk Send with Device Rotation
The safest approach rotates messages across multiple devices and adds a small random delay between sends. WhatsApp's algorithm looks for unnaturally uniform send patterns — randomizing delays (1–5 seconds between messages) mimics human behavior and significantly reduces ban risk.
import random
def send_bulk(recipients: list[str], message: str):
"""Send a message to a list of phone numbers with rate limiting."""
for i, phone in enumerate(recipients):
device_id = DEVICE_IDS[i % len(DEVICE_IDS)]
payload = {
"deviceId": device_id,
"to": phone,
"content": message,
"type": "text"
}
try:
resp = requests.post(BASE_URL, json=payload, headers=headers)
resp.raise_for_status()
print(f"Sent to {phone} via device {device_id}")
except Exception as e:
print(f"Failed for {phone}: {e}")
# Random delay: 1–5 seconds between messages
time.sleep(random.uniform(1, 5))
# Example: send to 500 contacts
contacts = ["+15551234567", "+15559876543"] # your list
send_bulk(contacts, "Hello! Your order has shipped.")Node.js Bulk Messaging with Queue
For production Node.js applications, use a queue-based approach to avoid overwhelming the API and to handle retries automatically. This example uses a simple promise chain for sequential sending:
const axios = require('axios');
const API_KEY = process.env.QUACKAPI_KEY;
const BASE_URL = 'https://quackapi.com/v1/messages/send';
const DEVICE_IDS = [1, 2, 3];
const sleep = (ms) => new Promise(r => setTimeout(r, ms));
async function sendBulk(recipients, message) {
for (let i = 0; i < recipients.length; i++) {
const deviceId = DEVICE_IDS[i % DEVICE_IDS.length];
try {
await axios.post(BASE_URL, {
deviceId,
to: recipients[i],
content: message,
type: 'text'
}, {
headers: { 'x-api-key': API_KEY, 'Content-Type': 'application/json' }
});
console.log(`Sent to ${recipients[i]}`);
} catch (err) {
console.error(`Failed: ${recipients[i]} — ${err.message}`);
}
// Random delay 1–4 seconds
await sleep(1000 + Math.random() * 3000);
}
}Anti-Ban Best Practices for Bulk WhatsApp
Only message people who have opted in to receive WhatsApp messages from you. Sending to cold lists is the fastest way to get reported and banned.
Start slowly: if you have a new WhatsApp number, warm it up by sending 50–100 messages on day 1, 200–300 on day 2, and gradually increasing. Do not send thousands of messages from a fresh number.
Personalize messages. Generic broadcast messages get reported at higher rates. Include the recipient's name at minimum.
Honor opt-outs immediately. Include a reply keyword like 'STOP' and remove anyone who uses it from future sends.
Spread sends across devices. The QuackAPI Professional plan supports 5 devices — use all of them to distribute your daily volume.
Avoid sending at unusual hours. Local daytime hours (9am–7pm in the recipient's timezone) have lower report rates than middle-of-night sends.
For tips on safe send rates and account protection, see our avoid WhatsApp number ban guide. For compliance and messaging etiquette, the WhatsApp API messaging best practices guide covers everything you need to stay safe.
Scheduling Bulk Sends with Cron
For recurring bulk sends (daily promotions, weekly newsletters), schedule your bulk send function using a cron job. This approach ensures you stay within daily limits and sends at optimal times.
# Using APScheduler for timed bulk sends
from apscheduler.schedulers.blocking import BlockingScheduler
scheduler = BlockingScheduler()
@scheduler.scheduled_job('cron', hour=10, minute=0)
def daily_promo():
"""Run every day at 10am."""
contacts = load_contacts_from_db()
send_bulk(contacts, "Today's offer: 20% off all orders!")
scheduler.start()High-Converting Bulk Message Templates
The message template you use dramatically affects delivery, open, and conversion rates. Generic broadcast messages get reported and ignored. Personalized, relevant, well-timed messages convert 3–5x better.
Abandoned cart recovery template (highest ROI): 'Hi {first_name}! You left {product} in your cart. It's still available for the next 24 hours: {cart_url}. Reply HELP for assistance.' This template converts at 25–35% — far higher than email equivalents. Use the QuackAPI API to send this immediately when your cart abandonment webhook fires.
Order confirmation template: 'Hi {first_name}! Order #{order_id} confirmed. Total: {currency}{amount}. We'll message you when it ships! — {store_name}.' Customers actually read these — 98% open rate means nearly every confirmation is seen.
Promotional announcement template: 'Hi {first_name}! {discount}% off today only for members. Use code {promo_code} at checkout: {link}. Reply STOP to unsubscribe.' Always include an opt-out mechanism. This alone reduces your report rate by 60% versus messages without it.
Reactivation campaign template: 'Hi {first_name}! It's been 30 days since your last visit. Here's 15% off to welcome you back: {link}. Expires in 48 hours.' Reactivation campaigns via WhatsApp see 20–30% conversion rates versus 3–5% via email.
Monitoring and Rate Limit Management
Configure a QuackAPI webhook to receive delivery receipts for every sent message. A delivery receipt tells you whether the message was delivered to the device and read. Track these metrics: delivery rate (target 95%+), read rate (WhatsApp averages 80%+), and reply rate.
If delivery rate drops below 90%, slow down your send rate — WhatsApp may be throttling your number. If you see a spike in undelivered messages, check whether the recipient numbers are valid WhatsApp accounts before sending. See WhatsApp notification use cases for monitoring dashboard examples.
For the QuackAPI Professional plan (5 devices, 1,000 msg/day/device), the maximum daily throughput is 5,000 messages. Spread sends evenly across devices using round-robin selection in your code. If you exceed the daily limit, QuackAPI queues the overflow for the following day rather than dropping messages — this protects your campaigns without data loss.
Set up alerting in your application for failed sends. Log each API response and alert your team if the failure rate exceeds 5% over a 30-minute window. This indicates a potential account issue that needs prompt attention.