API Reference

Get Messages by whatsapp number

get
https://live-mt-server.wati.io//api/v1/getMessages/

Get message history for a supported contact target. GET /{tenantId}/api/v1/getMessages/{target}.

Permissions

For API access tokens and OIDC tokens, satisfy at least one of: api, wati_integration:read, conversations:read. API access tokens may satisfy a listed scope through the configured scope hierarchy; OIDC tokens are checked against their scope claims. Legacy JWT authentication does not use this scope check. Authentication, role, tenant, and applicable feature or plan checks still apply. For HTTP 403, check the credential type, applicable scopes, roles, and workspace access; 403 does not always mean a missing scope. Authentication/authorization failures do not guarantee a JSON response body.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

WhatsApp Number with country code(e.g. 85264318721) or ContactId or Bsuid

string
required

Your WATI workspace (tenant) ID. This required path segment identifies the WATI account for legacy v1 and v2 API requests.

Query Params
string

Channel phone number with country code. Example, 85264318722

int32

Page Size

int32

Page Number

string

From. (Should be in UTC time) Example, 2022-11-27 10:26:58

string

To. (Should be in UTC time) Example, 2024-11-27 10:26:58

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

403

Authorization failed. Check the Permissions section for the credential-specific scope rules, and check roles and workspace access. The response may have no body; do not require a JSON error envelope.

Updated 3 months ago

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
text/plain
application/json
text/json

Updated 3 months ago