Skip to main content
GET
Call this from the visitor’s browser. It takes the embed’s public widget key in X-MITHUNAI-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-MITHUNAI-Visitor-Token. A missing token, another thread’s token, an unknown conversation ID and a malformed ID all return the same 404, so a visitor cannot probe for other visitors’ threads. A refusal made before the key and the origin are accepted (a missing or invalid key, an origin the deployment does not allow, or the per-address limit checked before the key is read) 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. Once the key is accepted and the origin is allowed, every response carries the header, refusals included, so your page can read a 404, a 429 and its Retry-After.
string
required
The conversation’s ID (UUID), from Start a widget conversation.
string
required
The deployment’s public widget key, mithunai_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.

Response

string
required
The conversation’s ID (UUID).
string
required
The assistant the deployment embeds.
string
required
The thread’s title.
string
required
active or archived.
string
required
idle when ready for a question, or awaiting_answer while an answer is being generated.
integer
required
Number of messages, questions and answers together.
string
required
ISO 8601 in UTC.
string
required
ISO 8601 in UTC.
object
required
{"type": "widget", "id": <deployment ID>}.
object
required
The metadata sent when the thread was started.
Last modified on November 7, 2026