Topolo Docs Topolo Platform
Open workspace

Xero migration status

Whether Xero is connected to this workspace, which organisation is selected, the organisations granted, and the last import.

Outcome

Whether Xero is connected to this workspace, which organisation is selected, the organisations granted, and the last import.

Before you start

  • Verify the intended environment, authenticated identity and specifically approved organization context.
  • The published application permission is migrations: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.migrations.xero.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/migrations/xero

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 the selected Books migrations result in the credential-scoped organization and applicable canonical workspace. Whether Xero is connected to this workspace, which organisation is selected, the organisations granted, and the last import.

Interpret the response

An unconnected workspace can return source:null. Inspect the connected source when present; use migrations.xero.status and tenant discovery rather than assuming an id always exists.

Inspect the actual response fields and retained identifiers for the selected organization/workspace. Whether Xero is connected to this workspace, which organisation is selected, the organisations granted, and the last import. Use the related published read actions when a returned record or ledger outcome needs further inspection; an HTTP 200 does not establish provider delivery or financial agreement.

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.migrations.xero.get --data @payload.json --json
topolo actions plan app_topolo_books.migrations.xero.get --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_books.migrations.xero.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.migrations.xero.get",
    "input": {},
    "resourceType": "workspace",
    "resourceId": "<exact granted workspace id>",
    "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

{
  "connected": false,
  "source": null,
  "tenants": [],
  "redirectUri": "https://books.test/api/integrations/xero/oauth/callback"
}

HTTP 200. Inspect the actual response fields and retained identifiers for the selected organization/workspace. Whether Xero is connected to this workspace, which organisation is selected, the organisations granted, and the last import. Use the related published read actions when a returned record or ledger outcome needs further inspection; an HTTP 200 does not establish provider delivery or financial agreement.

Successful response · HTTP 200

Input · payload.json:

{}

Captured response · HTTP 200

{
  "connected": true,
  "needsReconnect": false,
  "source": {
    "id": "mig_4b64fb4d789b4185826092dc29d333d2",
    "organization_id": "org_xero-route_muvnp1ej26",
    "workspace_id": "ws_xero-route_muvnp1ej26",
    "provider": "xero",
    "nexus_connection_id": "mig_6fe2b37a74164c5890686eb5ded71be5",
    "tenant_id": "tenant-a",
    "tenant_name": "Topolo Ltd",
    "tenant_country": null,
    "base_currency": null,
    "connected_by_user_id": "usr_test",
    "status": "active",
    "last_import_at": null,
    "last_import_summary": null,
    "last_error": null,
    "created_at": "2026-10-05T19:42:11.043Z",
    "updated_at": "2026-10-05T19:42:11.043Z"
  },
  "tenants": [
    {
      "tenantId": "tenant-a",
      "tenantName": "Topolo Ltd",
      "tenantType": "ORGANISATION"
    },
    {
      "tenantId": "tenant-b",
      "tenantName": "Second Co",
      "tenantType": "ORGANISATION"
    }
  ],
  "redirectUri": "https://books.test/api/integrations/xero/oauth/callback"
}

HTTP 200. Inspect the actual response fields and retained identifiers for the selected organization/workspace. Whether Xero is connected to this workspace, which organisation is selected, the organisations granted, and the last import. Use the related published read actions when a returned record or ledger outcome needs further inspection; an HTTP 200 does not establish provider delivery or financial agreement.

Verify the result

  • Inspect the actual response fields and retained identifiers for the selected organization/workspace. Whether Xero is connected to this workspace, which organisation is selected, the organisations granted, and the last import.
  • Use the related published read actions when a returned record or ledger outcome needs further inspection; an HTTP 200 does not establish provider delivery or financial agreement.

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.

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.