List the messages in a widget thread
Read the questions and answers in one widget thread, oldest first, for instance to restore the panel after a reload. Needs the widget key and visitor token.
GET
Call this from the visitor’s browser, for example to restore a thread after a page reload. It takes the embed’s public widget key in
X-ARUKZ-Widget-Key, and the browser’s Origin must be allowed by both the deployment’s allowed_origins and the platform-wide widget allowlist. See Website widget.
You must also send the thread’s X-ARUKZ-Visitor-Token. The token is checked before any message is read. A missing token, another thread’s token and an unknown conversation all return the same 404.
Messages come oldest first. Page through them with cursor; see Pagination. Render an assistant message as a finished answer only when its status is complete. An answer with abstained: true is a successful response in which the assistant said it could not find the answer in its knowledge; see How answers work.
When a request is refused, the response carries no Access-Control-Allow-Origin header, so in a cross-origin browser request fetch rejects with a network error instead of exposing the error body.
string
required
The conversation’s ID (UUID).
string
required
The deployment’s public widget key,
arukz_wk_….string
required
The visitor token returned when this thread was started.
string
required
Set by the browser. It must exactly match an origin allowed for this deployment. When you call
from outside a browser, set it yourself.
integer
default:"50"
How many messages to return, from 1 to 100.
string
The
next_cursor from the previous page. Omit it for the first page.Response
object[]
required
The messages, oldest first.
string | null
required
Pass as
cursor to get the next page, or null on the last page.boolean
required
Whether another page exists.
Last modified on September 26, 2026