Introduction
There is no single Buzzbip broadcast API endpoint. Programmatic broadcasts are built by sending an approved WhatsApp template (or SMS) to each contact in your audience. Each v2 send creates a whatsapp_bulk_group_id you can audit in message history.
Steps
Use this pattern for WhatsApp template broadcasts; adapt POST /api/sms/ for SMS.
- Authenticate with POST /api/login_check and send Authorization: Bearer on every API call.
- Define your audience: paginate GET /api/contacts/ or sync CRM contacts so each row has number and optional id.
- Trigger the broadcast: loop POST /api/v2/whatsapp/templates/{TEMPLATE_ID}/send per recipient (or POST /api/sms/ for SMS). Queue server-side with delays.
- Check delivery stats: GET /api/whatsapp/?whatsapp_bulk_group_id={id} for each send, or GET /api/sms/ history for SMS.
Code example
Send one approved template message per contact. Repeat in a server-side loop for the full audience. Store whatsapp_bulk_group_id from each response for delivery tracking.
curl --request POST \
'https://app.buzzbip.com/api/v2/whatsapp/templates/1289/send' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_JWT' \
--data '{
"to": "21696816277",
"country_code": "TN",
"body_params": ["Sam"]
}'Queue sends server-side with delays between batches to respect rate limits. For SMS broadcasts, use POST /api/sms/ in the same loop pattern.
What's next?
Related: api/v2/whatsapp-templates/send-template guides/whatsapp-v2-use-cases api/contacts
