Last verified 2026-11-09. Competitor details change, so confirm on their site before you decide.

QuackAPI vs WAHA

A hosted API you subscribe to, or an open-source engine you run yourself.

Short answer

WAHA is a free, self-hosted WhatsApp HTTP API that you run in Docker. QuackAPI is the same kind of linked-device approach, but hosted for you. Choose WAHA if you want control and zero licence cost and can run a server. Choose QuackAPI if you would rather not operate infrastructure.

Side by side

 QuackAPIWAHA
How it connectsLinked device: you scan a QR code with your own WhatsApp number. This is an unofficial method, not Meta's official API.Linked device (WhatsApp Web engines: WEBJS, NOWEB, GOWS). Not Meta's official Cloud API.
Who hosts itQuackAPI hosts it. You do not run any servers.You do. Self-hosted, typically with Docker.
Meta approval and templatesNot required. You can send any supported message type to a person who has agreed to hear from you.Not required.
Pricing modelFlat monthly plans: Starter (30-day free trial, then free with 10 messages a day), Professional $29/month, Enterprise $99/month. USD, paid with PayPal. No per-message fee.Core is free and open source with no message limit. A $5/month "Community" tier is a donation with no perks, per WAHA's support page.
Message typesText, image, video, audio, document, link, contact, location.Text, image, voice, video, file, sticker, location, contact, list, buttons, link preview, forward; polls and status are also documented.
WebhooksOne webhook URL per device. Events: message.received, message.sent, message.failed, message.unknown.Yes. Event payloads can differ between engines, so test before switching engines.
Multiple numbersMultiple devices per account. Limit depends on the plan (Starter 1, Professional 5, Enterprise 50).Unlimited sessions in Core, according to WAHA's docs.
Code examplescURL, JavaScript, Python, PHP, Java, C#, Go, Ruby, Rust, Kotlin, Swift, Dart, PowerShell (docs page).Integration pages for C#, Go, Java, JS/TS, Kotlin, PHP and Python; n8n, Chatwoot and Typebot guides.
Restriction riskReal. WhatsApp can restrict or ban numbers used with unofficial tools. See our Risk & Acceptable Use policy.WAHA's own homepage says WhatsApp does not allow unofficial clients, so use should not be considered totally safe.

Pricing

QuackAPI

Free, $29 or $99 per month

Starter is free. Professional is $29/month and Enterprise is $99/month, in USD. There is no per-message fee. See the pricing page for current device and daily message limits.

WAHA

WAHA: free (self-hosted)

WAHA Core has no licence fee. You pay for your own server, and spend time on updates and monitoring. WAHA changed its model in 2026: its docs say features that used to be in a paid Plus tier moved into the free Core from v2026.6.1, so older third-party articles about "Core vs Plus" may be out of date.

Choose WAHA if

  • You are comfortable running Docker and want full control of your data and server.
  • You need message types QuackAPI does not offer yet, such as stickers, polls or interactive buttons.
  • You want the lowest possible software cost and can handle uptime yourself.
  • You want an open-source codebase you can inspect and modify.

Choose QuackAPI if

  • You do not want to run, patch and monitor a server just to send WhatsApp messages.
  • You want a dashboard with QR pairing, device status and webhook logs ready to use.
  • You prefer a simple subscription with a free starting plan over managing hosting yourself.

Risk, plainly

Both tools use WhatsApp's linked-device protocol, so both carry the same account risk. Hosting model does not change that.

QuackAPI connects your own WhatsApp number as a linked device. This is not Meta's official API, and WhatsApp can restrict or ban numbers used this way. Read the Risk & Acceptable Use policy and the guide to avoiding bans before you send anything important.

Moving from WAHA to QuackAPI

  1. Connect your number in QuackAPI: create a device in the dashboard and scan the QR code.
  2. Replace WAHA's POST /api/sendText (which takes a chatId like 628123456789@c.us) with POST https://quackapi.com/v1/messages/chat and a JSON body of deviceId, to (digits with country code) and body.
  3. Send the x-api-key header instead of WAHA's own authentication.
  4. Point the device's webhook URL at your existing endpoint. QuackAPI's payloads have their own shape (see the webhook docs), so update your handler.
  5. Run both side by side on a test number before moving production traffic.

Endpoints and fields for QuackAPI are in the API docs.

Sources (2026-11-09)

These are the vendor's own pages. Where they disagreed with each other or we could not load them, we say so above instead of guessing. See something out of date? Tell us and we will check it.

Try QuackAPI on a free account

Connect a number with a QR code and send your first message with one request. No card needed for the Starter plan.