Base URL
POST /messages means POST https://api.watx.in/v1/messages.
The dashboard host proxies the same API at
https://app.watx.in/api/v1/…, which
is the form older integrations use and the form the dashboard’s own examples
show. Both reach the same service. Use https://api.watx.in/v1 for anything
new.Send your first message
Create a key in Settings → Developer → API keys with themessages:send scope (see
Authentication), then:
What you can do
What the API does not cover: managing templates, automations, flows, forms,
deals, sales documents and AI agents are dashboard features with no public
endpoints. Sending happens on WhatsApp — Instagram and website conversations
can be read through the API, but not replied to.
The feature called Campaigns in the app was called Broadcasts until
September 2026. The API kept the old name: the endpoints are
/broadcasts and
the scope is broadcasts:send.
Versioning
The version is in the path.v1 is the only version, and it is stable: the
endpoints, the response envelope and the field names above are what you can
build on.
Changes are additive. New fields appear on existing responses and new endpoints
appear under /v1 without a version bump, so parse leniently and ignore fields
you do not recognise. Renamed things keep their old name working alongside the
new one — message_id was added beside whatsapp_message_id, and API keys
issued under the old converse360_live_ prefix still authenticate.
Next
Authentication
Create a key, pick its scopes, send the header.
Requests and responses
The envelope, error codes, pagination, rate limits.
Webhooks
Events, signatures, retries.