Who uses a white label WhatsApp API?

• SaaS platforms that want WhatsApp as a native feature instead of an integration their customers have to set up elsewhere.
• CRMs and ERPs that need two-way conversations logged against contacts and deals.
• POS and booking systems sending receipts, order updates and appointment reminders.
• Customer support tools adding WhatsApp as an inbox channel.
• Automation platforms such as n8n or Zapier-style builders exposing WhatsApp as a step.
• Marketing agencies managing WhatsApp for many client brands from one system.

Fully API-first

Every feature is exposed through the REST API. You create sessions, fetch QR codes, send messages, manage contacts and groups and read logs programmatically, so WhatsApp fits into your existing backend and automation pipelines. The full reference is in the API documentation.

White label at the API level

Your end users interact only with your UI. They scan a QR code inside your dashboard and never see WasenderAPI anywhere in the flow.

No artificial limits

There is no fixed cap on the number of sessions, and you are not billed per message. You decide your own plan limits and margins, and you can scale horizontally as your user base grows.

Webhook-driven and real time

Inbound messages, delivery status updates and connection events arrive on your webhook instantly, so you can build inboxes, chatbots and alerts on top of live data.

Independent, isolated sessions

Each client runs in its own session with its own API key. One customer's problem does not spill over into another customer's account, which matters a lot once you have hundreds of tenants.

Cloud connectivity

Sessions keep working even if the user's phone temporarily loses connection or goes offline.

How billing works

• Credit balance: you top up a credit balance and session costs are drawn from it.
• Prorated new sessions: a session created mid-month is only charged for the remaining part of the month.
• Refund on delete: when you delete a session, the unused amount goes back to your balance.

This makes it simple to mirror your own billing: when a customer churns, you delete their session and stop paying for it.

Example monthly costs

What margin can you make?

Say you add WhatsApp to your platform as a $19/month add-on and 200 of your customers turn it on. Your revenue is $3,800 per month. Your WasenderAPI cost is $6 + (200 × $4.80) = $966 per month. That leaves roughly $2,834 per month of gross margin, and because there are no per-message fees, a customer who sends a lot of messages does not eat into it.

Step 1: Create a session for your customer

Account-level calls use your Personal Access Token. This request creates a session and points its webhook at your server (Create Session docs):

curl -X POST "https://www.wasenderapi.com/api/whatsapp-sessions" \
  -H "Authorization: Bearer YOUR_PERSONAL_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Customer 1042 - Acme Dental",
    "phone_number": "+447700900123",
    "account_protection": true,
    "log_messages": true,
    "webhook_url": "https://yourapp.com/webhooks/whatsapp",
    "webhook_enabled": true,
    "webhook_events": ["messages.received", "session.status", "messages.update"]
  }'

Step 2: Connect and display the QR code

Start the connection, then render the returned qrCode string as an image in your UI with any QR library (Connect docs, QR code docs):

curl -X POST "https://www.wasenderapi.com/api/whatsapp-sessions/{sessionId}/connect" \
  -H "Authorization: Bearer YOUR_PERSONAL_ACCESS_TOKEN"

# Refresh the QR code while the user is on the connect screen
curl "https://www.wasenderapi.com/api/whatsapp-sessions/{sessionId}/qrcode" \
  -H "Authorization: Bearer YOUR_PERSONAL_ACCESS_TOKEN"

Listen for the session.status webhook to know when the user has scanned and the session is connected, then update your dashboard.

Step 3: Send messages with the session API key

Each session has its own API key. Store it against the customer it belongs to and use it for that customer's messages:

curl -X POST "https://www.wasenderapi.com/api/send-message" \
  -H "Authorization: Bearer CUSTOMER_SESSION_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+447700900456",
    "text": "Hi Sarah, your appointment is confirmed for Tuesday at 10:00."
  }'

Step 4: Receive replies on your webhook

Incoming messages arrive as messages.received events and delivery or read updates as messages.update. Route each event to the right tenant by session, and you have a two-way WhatsApp channel inside your product.