Documentation Index
Fetch the complete documentation index at: https://docs.blocks.team/llms.txt
Use this file to discover all available pages before exploring further.
chat_thread_id — use it to build the polling URL for the assistant’s reply.
Follow-ups can be sent at any time, including while the agent is still working on a previous turn. They will interrupt the in-flight turn.
Request
Path parameters
The session to post the follow-up to.
Body
The follow-up user message.
Existing artifacts to attach to this message.
Profile reference or inline profile to apply to this turn. Same shape as in
Create Session.Response
Message ID for the user message you just posted.
The session this message belongs to.
The new thread created for this turn. Prefer
_links.final_message.href for polling — this field is exposed for cases where you need the thread ID directly.The task ID for the agent invocation triggered by this message.
Always
user for this endpoint.Always
message for this endpoint.Echo of the message body you posted.
Provider-supplied timestamp (epoch seconds). Typically
null for user messages.When the message was created.
When the message was last updated.
HATEOAS links — mirror those returned by
Create Session so you can reuse the same polling idiom for follow-ups.Errors
| Status | Code | Reason |
|---|---|---|
400 | BAD_REQUEST | The session has no prior messages, so no task_id can be resolved. Create the session via Create Session first. |
404 | NOT_FOUND | Session does not exist or belongs to a different workspace. |

