The Sessions API lets you start a conversation with a Blocks agent and stream its responses over plain HTTP. Every endpoint lives underDocumentation Index
Fetch the complete documentation index at: https://docs.blocks.team/llms.txt
Use this file to discover all available pages before exploring further.
/rest/v1, accepts and returns JSON, and authenticates with a workspace-scoped API key.
| Base URL | https://api.blocks.team |
| Auth header | Authorization: ApiKey <YOUR_API_KEY> |
| Rate limit | 100 requests / minute / API key |
1. Create a session and poll for the first reply
- Create a session —
POST /rest/v1/sessions. The response includes_links.final_message.href, a pre-built URL for polling the assistant’s reply. - Poll the URL —
GETit untilitemsis non-empty.
2. Send a follow-up
- Send a follow-up —
POST /rest/v1/sessions/{session_id}/messages. The response returns its own_links.final_message.href, the same shortcut as create. - Poll the new thread’s URL — same pattern as above.
Follow-ups can be sent at any time — including while the agent is still working — and will interrupt the in-flight turn.
session, headers, and BASE_URL are still in scope from the previous step.
Next steps
Create Session
Full request and response schema for
POST /rest/v1/sessions.Get Session Messages
List, filter, and poll messages on a session or a single thread.
Send Messages
Post follow-ups — they interrupt an in-flight session.
Get Session
Look up a single session by ID.

