Hub Chatt2.me API
Hub Chatt2.me is a unified messaging API that lets you send and receive messages across multiple channels — WhatsApp, Instagram, Facebook Messenger, Telegram, SMS, and Web Chatt — through a single, consistent interface.
Instead of integrating each platform separately, you connect your channels once and use the same request structure across all of them. Hub Chatt2.me handles the provider-specific complexity, authentication quirks, and delivery routing so you can focus on your product.
What you can do
- Send messages across all supported channels with a unified API
- Receive messages in real time via webhooks
- Track delivery status (sent, delivered, read) via
MessageStatusevents - Use rich content — interactive buttons, templates, location sharing, file attachments, and more
- Send payment requests (PIX, Boleto, payment link) and order status updates via WhatsApp
Base URL
| Environment | URL |
|---|---|
| Production | https://api.chatt2.me |
All API routes are prefixed with /v1.
Authentication
Every request must identify the Application using its API Key:
| Scheme | How to send |
|---|---|
| API Key | Header x-api-key: <your-api-key> |
See more details in Authentication.
Conventions
- All request and response bodies are JSON.
- IDs use the UUID v4 string format (e.g.
eba8d8ef-ec4d-41ad-825f-9a60ccda49bf). - The
fromfield in all message endpoints is the channel UUID registered in your Application — it is not a phone number or a username. - The
tofield is the recipient identifier in the specific channel (phone number, chat ID, PSID, etc.).
Errors
| Code | Meaning |
|---|---|
400 | Invalid payload — required field missing or incorrect format |
401 | Invalid or missing API key |
404 | Application, channel, webhook, or log not found for the credentials used |
Error responses may include errorMessage and errorCode fields in the body to aid diagnosis.
Next steps
- Authentication — how to obtain and use your API Key
- Concepts & Architecture — understand Applications, Channels, and Webhooks
- Sending messages — content types and request structure