Get workspace bootstrap

Get the signed Books workspace bootstrap payload.

Outcome

Get the signed Books workspace bootstrap payload.

Before you start

Verify the intended environment, authenticated identity and specifically approved organization context.
The published application permission is workspace:read. Bootstrap returns the authenticated user and organization; discover workspace grants independently.

Discover the target

topolo whoami --json
topolo actions get app_topolo_books.workspace.bootstrap --detail --json

Request

GET /api/bootstrap

Inspect and test this action. Save the reviewed input as payload.json; supply credential/resource context separately.

Input fields

Use an empty input object. Credential and resource context are separate.

Inspect nested fields and the complete input schema.

Effects

Returns the verified user and organization. It does not return a workspace catalog, grant projection or canonical workspace id.

Interpret the response

Read $.user.id for the returned workspace identifier. Empty collections and nullable fields do not discover a target.

Compare user.id and organization.id to whoami, then discover the applicable workspace independently through the canonical Auth resource catalog.

Inspect the success schema. CLI/MCP add their own transport envelope; CLI --detail requests the full result.

Worked examples

Actual Books route handlers and the exported Worker were exercised against five local SQLite D1 concern databases with all committed migrations, the real posting Durable Object and local R2. Route captures use synthetic verified Auth; Worker captures use synthetic Auth transports. Nexus, Brand, Notify, Pay, Mercury and Xero responses are explicitly simulated at the provider transport boundary. Captures prove local request/response behavior and canonical SDK projection, not live bank access, payment movement, email delivery, provider eligibility, tax compliance, encrypted custody, scheduled execution, deployment or production completion. Fixture identities, credentials, addresses and records authorize no live operation.

Run a reviewed request

Save the input from the selected worked example as payload.json. Validate and inspect the plan before calling the action; refused examples demonstrate errors and are not instructions to execute.

CLI:

topolo actions validate app_topolo_books.workspace.bootstrap --data @payload.json --json
topolo actions plan app_topolo_books.workspace.bootstrap --data @payload.json --json
topolo actions call app_topolo_books.workspace.bootstrap --data @payload.json --detail --json

MCP tool and arguments for the first successful example:

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_books.workspace.bootstrap",
    "input": {},
    "detail": true
  }
}

Refused response · auth_error

Input · payload.json:

{}

Captured response · HTTP 401

{
  "error": "API key validation failed"
}

HTTP 401. SDK error code auth_error. Authenticate in the intended organization again. Verify whoami and the exact Books application/workspace binding before retrying; do not switch identity to work around a refusal.

Successful response · HTTP 200

Input · payload.json:

{}

Captured response · HTTP 200

{
  "user": {
    "id": "usr_1",
    "email": "owner@example.com",
    "orgSlug": "acme",
    "role": "member",
    "orgId": "org_e2e_muvnp7qn2",
    "permissions": [
      "*"
    ]
  },
  "organization": {
    "id": "org_e2e_muvnp7qn2",
    "slug": "acme",
    "name": "Acme"
  }
}

HTTP 200. Compare user.id and organization.id to whoami, then discover the applicable workspace independently through the canonical Auth resource catalog.

Verify the result

Compare user.id and organization.id to whoami, then discover the applicable workspace independently through the canonical Auth resource catalog.

Errors and recovery

auth_error (HTTP 401): Authenticate in the intended organization again. Verify whoami and the exact Books application/workspace binding before retrying; do not switch identity to work around a refusal.

These are observed local refusals. Shared authentication, schema validation and resource authorization can also refuse before the route. Preserve the actual error, details and request id.

Recovery boundary

Repeat a read in the same authorized context; no state is changed.