List a conversation's messages
One conversation’s transcript, OLDEST FIRST. This is the only list on this API that ascends, and it ascends because a transcript has one legible order: a client reading newest-first would have to buffer the whole thread before it could render a single exchange in sequence. TOOL TURNS ARE NEVER SERVED. The assistant’s internal tool calls are how an answer was produced rather than part of the conversation, and they are excluded in the query so a page is never short. role is user for the shopper and assistant for the store. A HUMAN staff reply is stored as assistant too, deliberately, so the shopper’s widget renders it as a message from the store; read author_user_id to tell a person’s answer from the assistant’s. rating is the shopper’s own 1-5 stars, and null when they have not rated the reply. It is never 0.
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Path Parameters
Query Parameters
Rows per page. Out of range is a 400 rather than a silent clamp, so a client asking for more than 100 learns it did not get it.
1 <= x <= 100The next_cursor from the previous page. Opaque: decode nothing from it and construct nothing by hand, since its encoding is not part of this contract. Omit it to read the first page.