Documents

​
List the tabs of an in-house Space document, in order

A document holds tabs (Claude Docs files): the document itself is the first tab, and every other tab is a document id of its own, so the edit, view, export and comment operations take a tab id as their document_id. Any tab id resolves to its document.

GET
/v1/space/documents/{document_id}/tabs
curl -X GET "https://api.orchestor.io/v1/space/documents/%3Cdocument_id%3E/tabs" \  -H "Authorization: Bearer $API_KEY" \  -H "X-Workspace-ID: wks_abc123"
{  "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

Satisfy one of these options:

  • Session cookie
  • API key

Authentication details

cookie
wos-session

Browser session established by signing in to the web app. The server checks your workspace membership and permissions. Supply X-Workspace-ID for workspace-scoped operations. For server-to-server requests, use an API key when the operation supports it.

Path Parameters

document_idstringpathrequired
Pattern
^doc_[a-f0-9]{24}$

Headers

X-Workspace-IDstringheader

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"

Response

application/json

Tabs, first to last

dataSpaceDocumentTab[]required
data[]SpaceDocumentTab
data[].document_idstringrequired
data[].idstringrequired
data[].namestringrequired
data[].positionintegerrequired
data[].updated_atstringrequiredformat:date-time