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 workflow step.
• Marketing agencies managing WhatsApp for multiple client brands, subject to applicable WhatsApp policies and customer consent requirements.

API-first integration

Features are exposed through the REST API. You can create sessions, fetch QR codes, send messages, manage contacts and groups and receive events programmatically, allowing WhatsApp functionality to be integrated into your existing backend and automation pipelines. The full reference is available in the API documentation.

White label at the API level

Your end users interact with your product interface. They can scan a QR code inside your dashboard rather than being redirected to a separate WasenderAPI dashboard. However, your own product should clearly explain that the underlying integration is an independent, unofficial WhatsApp integration and is not Meta's official WhatsApp Business Platform.

Flexible session-based scaling

The Partner Program does not impose a fixed session limit in its standard pricing model, and there are no per-message fees. Actual usage remains subject to service availability, technical limitations, the Partner Program terms and any applicable WhatsApp restrictions or policies.

Webhook-driven and real time

Inbound messages, delivery status updates and connection events can be delivered to your webhook, allowing you to build inboxes, automations and notifications around live session data.

Independent sessions

Each customer can run in its own session with its own API key. Separating sessions can make tenant management and access control easier when your platform serves multiple customers.

Cloud-managed connectivity

Sessions are managed through the API infrastructure, allowing your application to interact with a connected session without requiring users to keep your application itself running. Availability can still depend on the session state, service availability and WhatsApp-side restrictions.

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 possible to align your infrastructure costs with the customers who actively use the WhatsApp feature. Your own billing, pricing and customer terms remain your responsibility.

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 would be $3,800 per month. At the $4.80 partner rate, your WasenderAPI cost would be $6 + (200 × $4.80) = $966 per month, before other operating costs. That would leave approximately $2,834 before other expenses such as infrastructure, support, payment processing, taxes and development.

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.