Documents
Add a tab to an in-house Space document, optionally with Markdown and blocks as in createSpaceDocument
The tab lands last. name holds at most 255 characters and no "/". markdown and blocks follow createSpaceDocument (<?claude block key?> tokens).
POST
/v1/space/documents/{document_id}/tabs
curl -X POST "https://api.orchestor.io/v1/space/documents/%3Cdocument_id%3E/tabs" \ -H "Authorization: Bearer $API_KEY" \ -H "X-Workspace-ID: wks_abc123" \ -H "Content-Type: application/json" \ -d '{ "blocks": {}, "markdown": "", "name": "string"}'{ "data": { "document_id": "<string>", "id": "<string>", "name": "<string>", "position": 0, "updated_at": "2026-01-01T00:00:00Z" }}Get your Orchestor API key
Create an API key in your workspace settings.
Authorizations
Authentication details
cookie
Headers
Workspace to access. With a workspace-scoped API key, the server derives this value from the key, so the header is optional. If supplied, it must match the credential workspace or the request returns 403 workspace_mismatch. For interactive session requests, supply this header to select a workspace where you are a member. A project ID cannot be used as a workspace ID.
Example
"wks_abc123"Bodyapplication/jsonrequired
Response
application/json