Outcome
List invoice-compatible Brand kits in this organization and the kit connected to this exact Books workspace.
Before you start
- Verify the intended environment, authenticated identity and specifically approved organization context.
- The published application permission is settings:read. Discover the exact granted canonical Books workspace and bind it separately from action input.
Discover the target
topolo whoami --json
topolo actions get app_topolo_books.settings.invoice_brand_connection.get --detail --json
topolo resources topolo-books --json
topolo workspaces list topolo-books --json
- Set BOOKS_WORKSPACE_ID to the exact granted workspace returned by discovery.
Request
GET /api/settings/invoice-brand-connection
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
- Reads same-organization Brand kits and the connection for this exact Books workspace without changing either app.
Interpret the response
An unbound workspace returns value:null. When a binding exists inspect value.connectionId and the Brand kit data; this read does not always return an identifier.
No verification is needed for this read.
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.settings.invoice_brand_connection.get --data @payload.json --json
topolo actions plan app_topolo_books.settings.invoice_brand_connection.get --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_books.settings.invoice_brand_connection.get --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --detail --json
MCP tool and arguments for the first successful example:
{
"tool": "topolo_read_action",
"arguments": {
"actionId": "app_topolo_books.settings.invoice_brand_connection.get",
"input": {},
"resourceType": "workspace",
"resourceId": "<exact granted workspace id>",
"detail": true
}
}
Successful response · HTTP 200
Input · payload.json:
{}
Captured response · HTTP 200
{
"options": [
{
"id": "brand_topolo",
"label": "Fixture Brand",
"readiness": "ready"
}
],
"value": null
}
HTTP 200. No verification is needed for this read.
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.
Verify the result
- No verification is needed for this read.
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
This action is read-only.
Related actions
- Connect invoice Brand kit: Connect one published, invoice-compatible Brand kit to this exact Books workspace.
- Get workspace settings: Read the workspace accounting, invoice identity and invoice approval-automation settings.
Evidence
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.