> ## Documentation Index
> Fetch the complete documentation index at: https://docs.watahub.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# API behavior

> Understand response formats and the limited Graph-compatible interface.

The public tenant API is separate from console and recovery interfaces.

## Watahub versus Meta

`POST /v1/messages` returns Watahub's `success`, `messageId`, `recipient` and `phoneNumberId`, not Meta's `wa_id` or `message_status`.

The Graph-compatible routes support message sends, media uploads and reads of tenant-owned media. They preserve Meta's bodies and statuses. They do not allow arbitrary Graph administrative calls.

The `/vN.N` version is accepted but ignored: the gateway uses its configured Meta API version. Changing the URL does not select another upstream version.

Read operation schemas rather than inferring fields from Meta examples. Meta-origin records can preserve additional fields; gateway-owned responses have explicit contracts. Keep IDs as strings and preserve returned cursors and identifiers.

## Other tools

Watahub also provides MCP at `/mcp` and a CLI. These are not defined by the REST OpenAPI. Check the current tool list and CLI help before depending on commands; this draft does not claim complete coverage of their changing catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.