Create a thread
Endpoint:POST /v1/threads Create thread
Create a message
Endpoint:POST /v1/threads/{thread_id}/messages Create message
Start a run
Once your thread has a message, start a run against it. SeekrFlow supports synchronous and streaming runs.Run synchronously
In synchronous mode, the agent processes the request and returns the complete response when generation is finished. Endpoint:POST /v1/threads/{thread_id}/runs Run agent
Run with streaming
In streaming mode, the agent’s response is sent back incrementally as it’s generated, allowing your application to display results in real time. Endpoint:POST /v1/threads/{thread_id}/runs/stream Run agent with streaming
Retrieve messages
Retrieve a message
Endpoint:GET /v1/threads/{thread_id}/messages/{message_id} Get message
Retrieve all messages from a thread
Endpoint:GET /v1/threads/{thread_id}/messages List messages
Manage threads
List threads
Endpoint:GET /v1/threads List threads
Retrieve a thread
Endpoint:GET /v1/threads/{thread_id} Get thread
Delete a thread
Endpoint:DELETE /v1/threads/{thread_id} Delete thread
Manage messages
Update a message
Endpoint:PATCH /v1/threads/{thread_id}/messages/{message_id} Update message
Delete a message
Endpoint:DELETE /v1/threads/{thread_id}/messages/{message_id} Delete message
Track file search sources
When an agent uses file search, each retrieved chunk’s source tracking fields are appended to the assistant message content:| Field | Description |
|---|---|
chunk_id | Unique chunk ID — use this to call the chunk endpoint for full Markdown provenance |
page | Source document page number (null for native Markdown or JSON) |
lines | Line range in the ingested Markdown (e.g. 42-67) |
section | Heading hierarchy path from document root to the chunk |
chunk_id with GET /v1/flow/vectordb/{database_id}/chunk/{chunk_id} to retrieve the file_id and download the original source document.