Low-cost WhatsApp API for developers, from $6 a month

A WhatsApp messaging API lets your backend send messages from events, such as an order, a booking or a sign-up. Nobody has to open a chat. With WASenderPlus your application shares connected numbers, pacing and suppression checks with the people answering customers.

When a customer replies, the agent needs the original message and the customer’s context. Keep that on the WhatsApp CRM record, and compare the messaging workflows that match your application. Decide who owns each reply before you switch on automated follow-ups.

Three models sit behind the words “WhatsApp API”. Meta’s WhatsApp Cloud API runs through the Business Platform, with onboarding and approved templates. Meta prices it per message, with rates that vary by message category and country. A WhatsApp Web gateway drives a linked session instead. The WhatsApp Business App is the phone app itself, built for one person answering chats.

WASenderPlus is an unofficial WhatsApp API: it links your number with a QR code and works through that WhatsApp Web session. You can send from your code, the web app, the Chrome extension or Sheets. Setup takes minutes, with no template approval and no Meta message fees. The session has to stay connected, and account restrictions remain possible.

Start with a connected number and a test recipient who has opted in. The examples above make an HTTPS POST with a bearer token in the Authorization header. The JSON body holds the recipient in to and the message in text.

Keep the API key on the server, never in browser code, repositories or screenshots. A successful response means the request was accepted, not that the message was delivered. Delivery arrives later as a webhook event or in the message status.

The PHP example uses the cURL extension, reads the key from an environment variable and encodes the payload with json_encode. Keep the recipient in the request body exactly as shown, and send from a server, never from the browser.

With Guzzle through Composer, keep the same endpoint, headers and fields. In Laravel, Symfony or WordPress, set a request timeout, inspect the response and catch exceptions. Do that before you connect live order events to a queue worker. Log failures with enough context to replay them safely.

Webhooks report delivered, read, replied and opted-out events to a URL you configure. Match each event to the outbound message and the contact before you update a record or start more work.

Build the handler to accept the same event twice and events that arrive out of order. Verify each request as the API docs describe, respond quickly, and do the heavy processing in a queue. Log failures so you can replay them later.

Plan each conversation around the format it needs: text, an image, a PDF invoice, a voice note or a location pin. In the web app, the extension and Sheets these sit side by side in one run, each personalised per contact.

Saved templates in WASenderPlus are reusable message bodies, not Meta-approved templates. An unofficial API does not need template approval. If you also run the official Cloud API elsewhere, its template rules still apply there. For API sends, the API docs list which formats each endpoint accepts.

Map purchase, payment, fulfilment and shipping events to separate messages. Shopify, WooCommerce or your own backend should supply the order context. That way agents never rebuild it by hand when a customer replies.

Check relevance before every send: cancel a dispatch notice if the order was cancelled, and route delivery exceptions to support. Confirm consent is still valid. A retry should look at the current order state, not the state when the first attempt failed.

A broadcast-to-reply workflow starts with an audience, an API-triggered message and a shared number. When a reply arrives it lands on the contact record. The agent who picks it up sees the original message, the order and the consent source.

Assignment and internal notes in the team inbox handle the handover between people. If your code also sends to the same customers, track which system owns the conversation. That stops an automated follow-up from landing on top of an agent’s reply.

Record the consent source, the date and the purpose before you import a contact. A phone number captured at checkout does not say what the customer agreed to receive. The glossary defines each term so your team uses them the same way.

Opt-outs are matched in 9 languages and stay suppressed after a re-import. For API integrations, check withdrawals again before a scheduled send or a retry. Require a fresh opt-in before messaging someone who said stop, and keep withdrawal records for later audits. U.S. businesses should also check applicable federal and state rules before automating promotional messages.

Plan bulk sending around consent, the age of the number and WASenderPlus’s default workload settings. Pacing controls when each message leaves the queue. It cannot stop a recipient from blocking or reporting you. WhatsApp also says it detects unwanted automated and bulk messaging, so restrictions remain possible with any unofficial API.

The defaults warm a new number over 2 weeks and space sends 4–40 seconds apart. They are WASenderPlus queue settings, not limits published by WhatsApp. Watch queue delays during the first campaigns, and read the sending guides before you scale a list.

Compare the workspace subscription with what an official provider would charge. Check Meta’s current per-message rates by message category and country. Providers bill in different ways, so a cheaper plan can cost more once message fees are added.

WASenderPlus starts at $6/mo with the REST API and webhooks included. The Team plan at $19/mo covers a team of any size with no per-agent billing. Add hosting and monitoring to the estimate before comparing the total with another tool.

Before launch, name an owner for key rotation and secret storage, and redact phone numbers from request logs. Keep separate keys for staging and production so a test run can never reach real customers.

Store the business event with each send so a retry cannot message the same customer twice. Test what happens when the linked session reconnects and when an opt-out arrives mid-campaign. Test the case where an agent has already answered the customer, too.