Solution · Unofficial WhatsApp API

Unofficial WhatsApp API to scale without limits

You get stuck on templates, Meta approval queues and fees that grow with every message you send. With D-API's unofficial WhatsApp API you connect real numbers in minutes and pay per instance, not per volume.

  • Billing: Per instance
  • Uptime: 99.9%
  • Meta approval: Not required
The problem

You shouldn't be solving this.

Problems D-API takes off your plate.

  1. Approvals and templates hold up your launch

    The official API requires Meta review, pre-approved templates and conversation windows that box in any creative automation.

  2. Per-message fees eat your margin

    Every send becomes a variable, unpredictable cost. As volume grows, the bill explodes and the ROI of the operation disappears.

  3. One blocked number takes down the whole operation

    Without isolation and a dedicated IP, a ban on one number spills over to the rest, and you have no plan B to keep conversations running.

How it works

From zero to production in four steps.

  1. Talk to sales

    Tell us your use case and get dedicated onboarding in a WhatsApp group to launch your operation with direct support.

  2. Connect your numbers

    Create one instance per number and scan the QR code. Each connection comes up with a dedicated proxy and its own IP.

  3. Integrate with the REST API

    Use your API key to send messages and native CTAs and to receive webhooks from any language or from the Node.js SDK.

    Read the docs
  4. Scale and monitor

    Track delivery, reads, response rate and number health, adding new instances as demand grows.

    See pricing

Works with the tools you already use

  • Node.js SDK
  • n8n
  • HTTPS/AMQP webhooks
  • Datacrazy CRM
  • Amazon S3/MinIO
What you get

Connect straight to WhatsApp, with no Meta approval and no per-message fees.

  • Multiple numbers in parallel

    Run several isolated WhatsApp numbers, one instance per number, all active at the same time without interfering with each other.

  • Dedicated proxy with its own IP

    Each connection gets a dedicated proxy with an exclusive IP, reducing the risk of your numbers being banned.

  • Real per-instance isolation

    A problem on one number does not affect the others: each instance is independent, so a single failure never turns into a domino effect.

  • High availability 24/7

    Continuous self-healing and infrastructure with 99.9% uptime keep your connections up without manual babysitting.

  • Webhooks with automatic retries

    Exponential backoff retries over HTTPS or AMQP/RabbitMQ keep events from getting lost. See the payloads in our Swagger.

  • No per-message fees

    Billing per active instance, with no volume fees: send as much as you need with a predictable monthly cost.

  • REST API in any language

    REST API authenticated by API key and documented in Swagger (OpenAPI 3), with an official Node.js SDK and an n8n community node.

FAQ

Frequently asked questions.

What is an unofficial WhatsApp API?
It is an API that connects directly to WhatsApp without going through Meta approval or using approved templates. You control real numbers, send messages freely and receive events by webhook, without the windows and restrictions of the official API.
Are there per-message fees?
No. Billing is per active instance, that is, per connected number. You can send the volume you need with no per-message fee, keeping costs predictable regardless of scale.
Can I connect multiple WhatsApp numbers?
Yes. Each number runs in an isolated instance, with a dedicated proxy and its own IP, all in parallel. A problem on one number does not affect the others, so you scale safely.
How do I reduce the risk of bans?
Each connection uses a dedicated proxy with an exclusive IP and real per-instance isolation. On top of that there is 24/7 self-healing and quick number swaps without redoing the integration, to keep the operation running if a number goes down.
Which language do I integrate with?
Any of them. The API is REST, authenticated by API key and documented in Swagger, so it works with any stack. There is also an official Node.js SDK and an n8n community node. Check the endpoints in Swagger.

Ready to go to production?

3-day free trial with full access. No credit card, no lock-in.