Overview
The read API lets your bot pull conversation history on demand — to build its own chat UI, backfill state after a restart, or debug — without keeping a perfectly synced copy of every webhook event. It is a narrow, provider-agnostic projection of the inbox; it never exposes internal rows, counters, or tokens. Permission:WhatsApp on both endpoints. Every query is scoped to the API key’s company —
a chat that belongs to another company returns a clean 404.
List conversations
Query parameters
Response
Conversation fields
List messages of a conversation
chatId returns 404.
Query parameters
Response
Message fields
Pagination shape
Both endpoints return the samepagination object:
Related
- Inbound Webhook — the real-time push side
- Send a Message