Avox Integrations

Every service Avox connects with - WhatsApp and Meta, your own servers and tools, payments, sign-in and email - with a setup guide for each.

Avox sits between WhatsApp and the rest of your business. Some integrations are built in and run for you (WhatsApp itself, PayPal, sign-in with Google or Facebook). Others you wire up yourself with the Avox API, using tools you already have. Every page below covers what the integration does, what you need, how to set it up, how to check it works, common errors and an FAQ.

WhatsApp and Meta#

The official Meta platform every Avox connection runs on.

Your systems#

Send messages from your own code, and manage the endpoint settings saved on each connection.

Avox APISend messages from your own systems with an API keyMessage forwardingGet new customer messages on your own serverNode.jsA plain Node.js webhook receiver and senderLaravelA Laravel route and HTTP client calling Avox's API

Apps and automation tools#

Send WhatsApp messages from the tools your team already uses, with their own webhook and HTTP features.

Payments, sign-in and email#

Built-in services that run your account.

Built in or built by you#

What every "built by you" integration needs#

1. 1

   A connected WhatsApp number

   See Getting started.
2. 2

   An API key for sending

   An Admin creates it in Settings > API Keys or on the connection's page. Start with a test key (avx_test_), which never sends anything, then switch to a live key (avx_live_). See API keys and Authentication.
3. 3

   A place to handle replies

   Customer replies arrive in the Inbox, and delivery statuses on Logs. Turn on Message forwarding to also get each new customer message on your own server. See Delivery statuses and replies.

Every request your keys make, and every message forwarded to your server, is listed in API logs in the dashboard - see API logs.

Not sure where to start? Avox API is the foundation the other "built by you" pages build on.

Last updated 10 October 2026