Tyxter Messaging
A developer-first WhatsApp Business Platform API. Send messages, receive webhooks, run sandbox scenarios, and route inbound automation — all with a single key.
Tyxter Messaging is the messaging product of the Tyxter platform. Use it to send transactional templates, run marketing broadcasts, receive inbound messages from WhatsApp users, and optionally hand automation off to an LLM you control.
These are the official Tyxter Messaging docs. Build from the routes and payload schemas in /openapi.json, /api-reference, and /llms.txt; public API calls use /v1/*.
Quickstart →
Send your first WhatsApp message in under three minutes.
Sandbox →
Build end-to-end without touching a real number. No cost, deterministic IDs.
New customer setup →
Dashboard handoff, agent key limits, and production readiness checks.
Webhooks →
Signed, retried delivery of every status change and inbound message.
API reference →
Full request + response shape for every endpoint, generated from the contract.
Status →
Live component health for the public Messaging API.
How it works
Tyxter Messaging is a modular monolith written in TypeScript. You talk to one HTTP API; we own the queue topology, the WhatsApp Cloud API integration, Brazilian number provisioning, billing, and the webhook delivery pipeline behind it.
Two environments, one key prefix
Every project has a sandbox environment and a production environment. Keys are strictly scoped by their prefix:
tx_sandbox_... → sandbox environment (free, deterministic)
tx_live_...... → production environment (billed in BRL)One HTTP base
Read the current API base URL from /.well-known/tyxter.json or from the servers list in /openapi.json.
Auth
Authorization: Bearer $TYXTER_API_KEYCore objects
| Object | Description |
|---|---|
message | An outbound or inbound WhatsApp message with its timeline of status events. |
message_batch | A broadcast of one template to many recipients. Runs on an isolated queue. |
template | Pre-approved marketing / utility / authentication copy. Submitted to Meta. |
flow | A WhatsApp Flow form; submissions fan out as flow.completed. |
phone_number | Salvy-provisioned or customer-connected WhatsApp number. |
contact | Minimal consent ledger. Opt-out blocks sends to that phone. |
llm_route | BYOK Anthropic/OpenAI configuration for inbound automation. |
webhook_endpoint | Where we deliver events. Signed with HMAC-SHA256. |
Next steps
- Follow the quickstart to send your first message.
- Read how webhooks work before you move to production.
- Browse the API reference for every endpoint.