Get Messages

What it is for: Lists messages for a channel, forum topic, or community context so an integration can audit or sync conversation history.
How to use it: Send a GET request to /v1/messages with the request body, query parameters, or multipart fields shown below. Authorization: Bearer <apiKey>. Community API keys require the matching messaging permission. User API keys can also be used for supported message actions and may be channel-restricted.
Required permission: getMessages.
Successful response: HTTP 200. The body follows the endpoint schema; many integration endpoints wrap the useful payload under data with status and message.
Common error states:

400 invalid request body, query, ObjectId, pagination, file format, or missing required field.

401 missing, invalid, expired, or insufficient API key/token.

403 key is valid but cannot access this community/channel/user/resource, where supported by the service.

404 target resource, route, or community-scoped record was not found.

409 duplicate or conflicting state for create/update operations, where applicable.

500 unexpected Returning.AI service error.

Verified response note:
A live non-destructive test on 2026-05-19 returned HTTP 200 with { status, message, data }; data contained total and messages, and each message exposed id, message, user, channel, and timestamp.

{ "status": "success", "message": "messages fetched successfully", "data": { "total": 10, "messages": [ { "id": "689b908502ad38f", "message": "Hi", "user": { "user_id": "1243", "email": "johndoe@gmail.com" }, "channel": { "channel_id": "663347f4361726479c6", "name": "Rules" }, "timestamp": "2025-08-05T01:39:43.561Z" }, ... { "id": "6633473f8a0f479cf", "message": "Good morning everyone!", "user": { "user_id": "1243", "email": "johndoe@gmail.com" }, "channel": { "channel_id": "66334714361726479c6", "name": "General" }, "timestamp": "2024-05-02T07:56:47.276Z" } ] } }

Request

Responses