Skip to main content
GET
List messages

Request contract

  • Method and path: GET /apis/v1/social/inbox/conversations/{conversationId}/messages
  • Availability: enabled
  • Request URL template: https://api.aisa.one/apis/v1/social/inbox/conversations/{conversationId}/messages
  • conversationId: path; required
  • accountId: query; required
  • limit: query; optional
  • cursor: query; optional
  • sortOrder: query; optional
  • Runtime facts: 99acb5bddbedc8d3352e7c4fef86c3e6d8852c14772bcd18dbcf415237a642bd
Complete OpenAPI definition Effective request and pricing declaration (including authentication and referenced schemas):

Cost and request rules

A request reference price is not currently available; use a request quote where supported. Account-specific pricing and final settlement may differ. Published reference values are not an account-specific quote or a settled charge. For endpoints supporting X-AISA-Cost-Mode: quote, obtain a free quote for your exact request before execution; reconcile the settled cost with response metadata and Usage Logs. USD amounts use 1,000,000 integer micro-USD per dollar.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

conversationId
string
required

Opaque conversation identifier, accepted verbatim from the list endpoint or from the conversationId on inbox webhooks. Format not to be assumed.

Query Parameters

accountId
string
required

One of your social accounts (acc_...).

Pattern: ^acc_[0-9A-Za-z]{22}$
limit
integer
default:100

Number of messages to return per page. Default 100, max 100.

Required range: 1 <= x <= 100
cursor
string

Opaque pagination cursor. Pass pagination.nextCursor from a prior response verbatim: a cursor we cannot parse returns 400 rather than silently restarting from the first page.

sortOrder
enum<string>
default:asc

Order of returned messages. Default asc (oldest first, chat style). X, Instagram, Telegram, WhatsApp and Reddit honor this order across cursor pages. For Facebook and Bluesky, only intra-page ordering is affected. Pages always walk newest→oldest. See sortOrderApplied in the response.

Available options:
asc,
desc

Response

Messages in conversation

lastUpdated
string<date-time>
messages
object[]
pagination
object
sortOrderApplied
enum<string>

Sort order actually applied to the returned page. May differ from the requested sortOrder for Facebook and Bluesky (always desc regardless of request).

Available options:
asc,
desc
status
string