Hydrate one page of a Cortex Agent Thread's message history, oldest first.
Ownership is checked against dvt's own agent_threads index BEFORE any engine call — another user's thread (even in the same org) 404s, and the engine is never called. On a 200, content is read through from Snowflake on demand for this one request and is never stored by dvt (ADR-0082 D6 no-chat-content) — the same no-persistence rule every other /v1/agent/* route in this file follows. Messages are returned oldest first (Cortex's own Threads REST API returns them newest first; this endpoint reverses that order). The server strips the <dvt_context> block it prepends to popup user turns from user message text (see POST /v1/agent/run), so clients never see it.
Request
- Base URL: http://localhost:8080
- URL: http://localhost:8080/v1/agent/threads/{id}/messages
- Auth: one of:
- API key in cookie dvt_session
- HTTP bearer
Query parameters
Fetch the page older than this Snowflake message id (keyset pagination). Digits only.
Response
Messages, oldest first.
Changes
No recorded changes to this operation across all 1 revision of this API.