Use case · Automation

The WhatsApp API for automation that does not break mid-flow.

You build flows in n8n, Make or Zapier that need to run 24/7 in production. D-API is the stable WhatsApp API infrastructure that delivers messages and events without waking you up at night.

  • Official node: n8n
  • Events: In real time
  • Protocols: REST + AMQP
The problem

You shouldn't be solving this.

Problems D-API takes off your plate.

  1. Workflows breaking halfway

    An unstable API makes n8n fail in production and you lose messages without noticing.

  2. Unstructured events

    Poorly formatted webhooks force your flow into manual parsing all the time.

  3. Unofficial nodes

    Community-maintained integrations break every time the API changes.

How it works

From zero to production in four steps.

  1. Install the node

    In n8n Settings → Community Nodes, add the official n8n-nodes-d-api package.

    npmjs.com/package/n8n-nodes-d-api
  2. Connect the credential

    Paste your instance API key and you are done: sending and triggers work right away.

  3. Build your flow

    Use the send, chat listing and webhook trigger nodes with typed fields.

  4. Scale or migrate

    Switch to REST, the SDK or RabbitMQ as your flow grows, with the same API key authentication.

    docs.d-api.cloud

Works with the tools you already use

  • n8n
  • Make
  • Zapier
  • RabbitMQ
  • Claude and OpenAI
What you get

The stable API your n8n, Make and Zapier flows were missing.

  • Official n8n community node

    The n8n-nodes-d-api package is maintained by D-API and kept in sync with our public API.

  • Webhooks with automatic retries

    Structured message, status and connection events delivered over HTTPS or AMQP, with exponential backoff retries for anything not acknowledged.

  • Low latency

    Sending and receiving with millisecond latency, with no intermediate queue slowing things down.

  • Dedicated proxy

    Each connection gets a proxy with its own IP, managed automatically by D-API, reducing the risk of bans.

  • Routing by type

    Split events into different queues using RabbitMQ routing keys.

  • AI-ready

    Plug in Claude, OpenAI or n8n AI agents with typed conversation context.

  • Documented REST

    Explore every endpoint in the Swagger docs, with JSON request and response examples ready to test in the browser.

  • Delivery monitoring

    Message status exposed via webhook (sent, delivered, read, failed) so your flow reacts in real time.

  • Dedicated onboarding

    We set up a WhatsApp group with your team to answer questions and unblock your flow implementation, all at no cost.

FAQ

Frequently asked questions.

Where can I find the API docs?
In the Swagger docs (OpenAPI 3). You test endpoints right in the browser and export collections to Postman or Insomnia.
What is the difference between the n8n node and REST?
The node speeds up development with typed fields and built-in authentication. REST, described in our docs, gives you full control. Both use the same API.
Can I make sure messages are delivered?
Yes. D-API retries with exponential backoff and exposes delivery status via webhook. You can combine it with RabbitMQ for end-to-end guarantees.
Does it work with Make and Zapier?
Yes. Because it is standard REST with API key authentication in the Authorization header, it works on any platform that speaks HTTP: Make, Zapier, Pipedream, Bubble and others.

Ready to go to production?

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