Genuka WA vs 360dialog: WhatsApp API compared

Genuka WA and 360dialog both connect you to Meta's official WhatsApp Business Platform with no markup on Meta's rate cards (with one exception at 360dialog, covered below). 360dialog is a Meta Business Solution Provider charging from €49 per number per month, paid by card. Genuka WA is a Meta Tech Provider charging from 5,000 FCFA per number payable by Mobile Money, or €19 by card.

Last updated October 8, 2026

Genuka WA vs 360dialog at a glance

How much does each cost per WhatsApp number?

Both models put a flat fee on the number and leave the message cost to Meta. The difference is in what the fee includes. 360dialog's Regular licence is €49 per number per month, and their pricing page sets no message allowance on it. Genuka WA's tiers cost less at the start and include a monthly allowance of outbound messages per paid number, pooled across the account: each number added to the plan adds its allowance, whether or not it is connected. Incoming messages are never counted.

Provider cost for sending from one number, monthly billing, Meta's fees excluded. The Genuka WA column shows the cheapest setup for each volume:

Provider cost for five numbers, monthly billing, Meta's fees excluded:

On Genuka WA the allowance is pooled: five Growth numbers share 25,000 outbound messages a month. Past the allowance, the API refuses sends (402 plan_limit_messages) until you add numbers, move up a tier or reach the next period. Yearly billing lowers our base price to €15, €39 and €119 a month (3,000, 8,000 and 25,000 FCFA). The full grid is on the pricing page and, in Markdown, at /pricing.md.

Who pays Meta, and how?

The rates are Meta's in both cases: since July 1, 2025 Meta charges per delivered template, by category and by the recipient's country code, and since October 1, 2026 it also charges service messages (free-form replies inside the 24-hour window) and utility templates sent inside that window. Messages in the 72-hour free entry point window opened by a Click to WhatsApp ad stay free.

The payment path differs. A BSP such as 360dialog can extend Meta's credit line to its clients: 360dialog deducts Meta's charges from a prepaid balance per number, which you top up by card in its Hub, manually or automatically below a threshold. A Tech Provider has no credit line, so with Genuka WA the business adds its own payment method to its WABA in WhatsApp Manager and Meta bills it directly. Until one is added, template sends fail with Meta error 131042.

How do I connect a number on each platform?

Both use Meta's Embedded Signup: the business logs in with Facebook, picks or creates its WABA, and registers the number. Both support Meta's coexistence mode, so a number already on the WhatsApp Business app keeps the app for one-to-one chats. Meta's conditions apply everywhere: app version 2.24.17 or later, history synced within 24 hours, and a fixed 20 messages per second for that number. On Genuka WA, step by step: Coexistence.

For platforms that onboard numbers on behalf of clients, 360dialog sells a separate Partner Platform starting at €250 a month plus a fee per channel. On Genuka WA, this comes with the Scale tier (€149 or 30,000 FCFA a month, then €6 or 1,800 FCFA per extra number), with no separate partner plan: the dashboard gives you a connect link to send to your clients, a list of your clients and their sub-accounts. Tag each client with ?ref=<your-client-id> and find their number with GET /api/v1/connections?externalRef=…. White-label branding is included from Growth. See Connecting a number.

How different are the API and the webhooks?

360dialog exposes Meta's Cloud API almost as-is: you post Meta's payload to https://waba-v2.360dialog.io/messages with your D360-API-KEY. Genuka WA wraps the same Cloud API in a shorter body, so the common cases stay readable, and keeps two doors open to Meta's raw format: a template.components array is forwarded untouched, and a raw field takes any Cloud API message fragment. Template definitions also use Meta's components array verbatim, so the templates you already wrote carry over. See Sending messages and the API reference.

On webhooks, 360dialog forwards Meta's payloads, signed with x-360dialog-signature; you must answer 200 within 5 seconds, and Meta retries failed deliveries for up to 7 days. Genuka WA posts one event per request, with Meta's raw value inside an envelope that names the business and the number, signed with X-Genuka-Signature (HMAC-SHA256 over the timestamp and the raw body). You get 10 seconds to answer, 5 retries over about 8.5 hours, and a replay button in the dashboard. See Webhooks.

Both also serve AI agents. 360dialog hosts an MCP server that manages accounts, channels, templates, webhooks and balance, and publishes its docs as llms.txt and Markdown. Genuka WA provides an MCP server, @genuka/whatsapp-mcp (being published to npm), a /llms.txt index and a Markdown version of every docs page: see AI agents.

What changes in my code if I move from 360dialog?

A template send on 360dialog, from their documentation:

curl -X POST https://waba-v2.360dialog.io/messages \
  -H "D360-API-KEY: {{api-key}}" \
  -H "Content-Type: application/json" \
  -d '{
    "messaging_product": "whatsapp",
    "to": "PHONE_NUMBER",
    "type": "template",
    "template": { "name": "hello_world", "language": { "code": "en_US" } }
  }'

The same send on Genuka WA. Your API key covers every number on the account, so the body names the sender with a connectionId (list yours with GET /api/v1/connections):

curl -X POST https://wa.genuka.com/api/v1/messages \
  -H "Authorization: Bearer $GENUKA_WA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "connectionId": "con_1",
    "to": "+237690000001",
    "template": { "name": "hello_world", "language": "en_US" }
  }'

When should you choose 360dialog instead?

• One number, high volume, paid in EUR. A flat €49 licence with no message allowance beats our plans above 5,000 outbound messages a month on that number.
• You want a sandbox. 360dialog has one (200 messages to your own number); Genuka WA does not.
• You want Meta's fees paid through your provider. 360dialog's prepaid balance means no payment method to set up in WhatsApp Manager.
• You want 24/7 human support with a first-response SLA on every number, from the entry plan.

When is Genuka WA the better fit?

• You pay in FCFA, by Mobile Money. Plans are priced in XAF and XOF; card is available in EUR and USD.
• You run several numbers. Extra numbers cost €6 to €9 a month (1,800 to 2,500 FCFA) depending on the tier, instead of a full licence each.
• You onboard numbers for your clients. From the Scale tier, the connect link, ?ref= tagging and client sub-accounts are included, with no separate €250-a-month partner plan.
• You would rather not manage a prepaid balance. Meta bills the WABA's own payment method, so there is no per-number balance to top up.
• You want French documentation. All API docs exist in French and English (the TypeScript SDK guides are English only).

FAQ

Does 360dialog mark up Meta's WhatsApp fees?

Not on Meta's rate cards. Their documentation adds one exception: marketing content sent through the standard messages endpoint, instead of Meta's Marketing Messages API, carries a 7% surcharge on Meta's rate. Their API reference adds that the /messages endpoint routes to the marketing endpoint automatically when applicable. Genuka WA never bills messages at all: Meta charges your WABA directly.

Is Genuka WA cheaper than 360dialog?

For one to a few numbers with moderate volume, yes: our tiers start at €19 and extra numbers cost €6 to €9 a month. For a single number sending more than 5,000 outbound messages a month, paid in EUR, 360dialog's €49 Regular licence costs less.

Can I keep the WhatsApp Business app with either provider?

Yes. Both support Meta's coexistence mode: the app keeps working for one-to-one chats while the API sends at scale, with history kept in sync. Only a number on regular consumer WhatsApp has to be freed first.

Can I pay with Mobile Money?

On Genuka WA, yes, in XAF or XOF. 360dialog's payment documentation lists Visa, Mastercard and American Express cards. Meta's own message fees are paid to 360dialog's prepaid balance by card, or, with Genuka WA, to Meta through the payment method on your WABA.

Will my 360dialog code work on Genuka WA?

Mostly with small changes. Template definitions use Meta's components array on both, and Genuka WA accepts raw Cloud API fragments through template.components and raw. What changes is the authentication header, the base URL and the connectionId that names the sending number.

Sources

Read on October 8, 2026.

• 360dialog, pricing: https://www.360dialog.com/pricing
• 360dialog, Pricing (docs): https://docs.360dialog.com/docs/get-started/pricing
• 360dialog, Payments: https://docs.360dialog.com/docs/get-started/payments
• 360dialog, Funds: https://docs.360dialog.com/docs/hub/funds
• 360dialog, About: https://docs.360dialog.com/docs/get-started/about
• 360dialog, Coexistence: https://docs.360dialog.com/docs/hub/embedded-signup/whatsapp-coexistence
• 360dialog, Sandbox: https://docs.360dialog.com/docs/get-started/sandbox
• 360dialog, 360Dialog MCP: https://docs.360dialog.com/docs/get-started/mcp
• 360dialog, Send and receive messages: https://docs.360dialog.com/docs/guides/send-and-receive-messages
• 360dialog, Messaging API reference (messages): https://docs.360dialog.com/docs/messaging-api/api-reference/messages
• 360dialog, Webhooks: https://docs.360dialog.com/docs/messaging/webhook
• 360dialog, Meta Business Agent webhooks (signature): https://docs.360dialog.com/docs/mba/webhooks
• 360dialog, documentation index: https://docs.360dialog.com/llms.txt
• Meta, WhatsApp Business Platform pricing: https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing
• Meta, Pricing updates for service and utility messages: https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing/non-template-messages
• Meta, Solution Partners and Tech Providers: https://developers.facebook.com/documentation/business-messaging/whatsapp/solution-providers/overview
• Meta, Onboarding customers as a Tech Provider: https://developers.facebook.com/documentation/business-messaging/whatsapp/embedded-signup/onboarding-customers-as-a-tech-provider
• Meta, Onboarding WhatsApp Business app users (coexistence): https://developers.facebook.com/documentation/business-messaging/whatsapp/embedded-signup/onboarding-business-app-users
• Meta, Error codes: https://developers.facebook.com/documentation/business-messaging/whatsapp/support/error-codes