List space documents

Outcome

List active documents in one documentation space.

These examples were captured from the local Worker. Deployment, publication and retrieval are verified separately for each environment; local examples do not establish external provider delivery.

Before you start

• Inspect the credential identity with topolo whoami and the exact action with topolo actions get before preparing input.

• Discover an accessible Docs workspace with topolo resources topolo-docs and topolo workspaces list topolo-docs. Pass workspace resource type and identifier separately from action input.

• The published required permission is docs:read; the active credential and resource binding must authorize the call.

Discover the target

topolo actions get app_topolo_docs.spaces.documents.list --detail --json
topolo resources topolo-docs --json
topolo workspaces list topolo-docs --json
Discover spaceId with app_topolo_docs.spaces.list in the selected workspace.

Input fields

Interpret the response

documents contains non-archived records in the specified space. currentVersionId and publishedVersionId are separate pointers; draft changes are not necessarily the published page.

Worked examples

The following inputs and responses were captured from the local Docs worker fixture. Auth and Nexus dependencies are simulated. Identifiers, URLs and timestamps are illustrative fixture values. Discover your own identifiers and choose an appropriate test resource; copying a fixture identifier does not make it valid in your environment. For workspace-bound calls, set DOCS_WORKSPACE_ID to the identifier returned by resource discovery. Run validation and planning first; the final call requires the intended effect to be authorized.

Minimal example

Save the input as payload.json:

{
  "spaceId": "docspace_a09c96df-e507-4751-89c8-e6a99e496d0d"
}

CLI:

topolo actions validate app_topolo_docs.spaces.documents.list --data @payload.json --json
topolo actions plan app_topolo_docs.spaces.documents.list --resource-type workspace --resource-id "$DOCS_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_docs.spaces.documents.list --resource-type workspace --resource-id "$DOCS_WORKSPACE_ID" --data @payload.json --json

MCP tool and arguments:

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_docs.spaces.documents.list",
    "input": {
      "spaceId": "docspace_a09c96df-e507-4751-89c8-e6a99e496d0d"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>"
  }
}

Captured local response · HTTP 200:

{
  "documents": [
    {
      "id": "doc_de0efe08-781e-4e60-9d7a-2a48b6dd4dd4",
      "organizationId": "org_fixture",
      "workspaceId": "ws_fixture",
      "spaceId": "docspace_a09c96df-e507-4751-89c8-e6a99e496d0d",
      "sectionId": "docsec_9c57d921-baf8-455c-89a0-5abb407cb339",
      "sectionPosition": 0,
      "parentId": null,
      "slug": "rotate-token",
      "title": "Rotate an integration token",
      "summary": "",
      "status": "draft",
      "sourceKind": "native",
      "ownerAppId": null,
      "currentVersionId": "docver_cef00930-d087-4485-98bc-0f335d96fd80",
      "publishedVersionId": null,
      "createdByUserId": "usr_fixture",
      "createdAt": "2026-10-03T08:07:30.565Z",
      "updatedAt": "2026-10-03T08:07:30.742Z",
      "publishedAt": null
    }
  ]
}

documents contains non-archived records in the specified space. currentVersionId and publishedVersionId are separate pointers; draft changes are not necessarily the published page.

Workflow example

Save the input as payload.json:

{
  "spaceId": "docspace_a0013653-dabf-4831-8c11-6405b39664ca"
}

CLI:

topolo actions validate app_topolo_docs.spaces.documents.list --data @payload.json --json
topolo actions plan app_topolo_docs.spaces.documents.list --resource-type workspace --resource-id "$DOCS_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_docs.spaces.documents.list --resource-type workspace --resource-id "$DOCS_WORKSPACE_ID" --data @payload.json --json

MCP tool and arguments:

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_docs.spaces.documents.list",
    "input": {
      "spaceId": "docspace_a0013653-dabf-4831-8c11-6405b39664ca"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>"
  }
}

Captured local response · HTTP 200:

{
  "documents": [
    {
      "id": "doc_453b15f4-06fc-4366-ae42-adf1f10d9d38",
      "organizationId": "org_fixture",
      "workspaceId": "ws_fixture",
      "spaceId": "docspace_a0013653-dabf-4831-8c11-6405b39664ca",
      "sectionId": "docsec_37f4c4e1-d416-47d7-ad57-d0a38fb678c4",
      "sectionPosition": 0,
      "parentId": null,
      "slug": "rotate-token",
      "title": "Rotate an integration token",
      "summary": "",
      "status": "draft",
      "sourceKind": "native",
      "ownerAppId": null,
      "currentVersionId": "docver_de2b1e18-55d5-4793-b71f-51bc27b78c84",
      "publishedVersionId": null,
      "createdByUserId": "usr_fixture",
      "createdAt": "2026-10-03T08:07:34.003Z",
      "updatedAt": "2026-10-03T08:07:34.157Z",
      "publishedAt": null
    }
  ]
}

documents contains non-archived records in the specified space. currentVersionId and publishedVersionId are separate pointers; draft changes are not necessarily the published page.

Verify the result

• Require every returned document.spaceId to match spaceId. Read currentVersionId and publishedVersionId separately before selecting content.

Errors and recovery

• HTTP 401 · authentication_required: Authenticate again or provide a valid Topolo API key.

• HTTP 403 · permission_denied: Grant the credential permission docs:read and the required resource binding.

• HTTP 429 · rate_limited: Wait for Retry-After when present, then retry without parallel duplicate calls.

• HTTP 422 · invalid_input: Correct the payload using inputSchema, then validate before retrying.

• HTTP 503 · dependency_unavailable: Retry the action. If it continues, inspect the structured error details using the request ID.

This action does not change service state.

Evidence boundary

These examples establish local handler behavior and schema validity. They do not establish runtime permission parity, a deployed development/staging result or production completion. Preserve the actual request identifier and perform the verification reads after an authorized live call.