Outcome
List the Pay checkout sessions created for an invoice, newest first, including their amount, settlement state and stable Books customer-page URL without exposing the provider checkout URL.
Before you start
- Verify the intended environment, authenticated identity and specifically approved organization context.
- The published application permission is invoices: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.invoices.payment_sessions.list --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.
- documentId: Exact document.id from invoices.list/get or bills.list/get, as appropriate to this action; the displayed invoice number is distinct.
Request
GET /api/invoices/{documentId}/payment-sessions
Inspect and test this action. Save the reviewed input as payload.json; supply credential/resource context separately.
Input fields
| Field | Required | Meaning | Schema and constraints |
|---|---|---|---|
documentId | Required | Exact document.id from invoices.list/get or bills.list/get, as appropriate to this action; the displayed invoice number is distinct. | {"type":"string","minLength":1} |
Inspect nested fields and the complete input schema.
Effects
- Reads checkout history and the stable Books customer-page URL without exposing the provider checkout URL or changing Books or Pay.
Interpret the response
Read $.sessions[].id for the returned invoice_payment_session identifier. Empty collections and nullable fields do not discover a target.
No verification is needed for a 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.invoices.payment_sessions.list --data @payload.json --json
topolo actions plan app_topolo_books.invoices.payment_sessions.list --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_books.invoices.payment_sessions.list --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.invoices.payment_sessions.list",
"input": {
"documentId": "doc_f8852615bef8424d9e4d87f8fb6b2592"
},
"resourceType": "workspace",
"resourceId": "<exact granted workspace id>",
"detail": true
}
}
Refused response · auth_error
Input · payload.json:
{
"documentId": "doc_9f2a"
}
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:
{
"documentId": "doc_f8852615bef8424d9e4d87f8fb6b2592"
}
Captured response · HTTP 200
{
"sessions": [
{
"id": "ips_b81e20e56bf84c6ca2e3c05a7061dabc",
"organization_id": "org_invoice-pay-route_muvnpf1314",
"workspace_id": "ws_invoice-pay-route_muvnpf1314",
"document_id": "doc_f8852615bef8424d9e4d87f8fb6b2592",
"merchant_id": "mrc_books",
"order_id": "books-doc_f8852615bef8424d9e4d87f8fb6b2592-0-mrc_books-mpa_checkout_books-0",
"session_id": "cs_invoice",
"amount_minor": 12000,
"currency": "GBP",
"status": "open",
"provider_status": "open",
"payment_id": null,
"created_at": "2026-10-05T19:42:28.717Z",
"updated_at": "2026-10-05T19:42:28.717Z",
"completed_at": null,
"provider_account_id": "mpa_checkout_books",
"payment_url": "https://books.test/invoice/ish_a86b94eb205442da85b4c30848fbfca2"
}
]
}
HTTP 200. No verification is needed for a read.
Verify the result
- No verification is needed for a 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
- Check invoice payment: Verify a hosted checkout directly with Topolo Pay. A completed payment is recorded once against the invoice and posted through undeposited funds for later payout reconciliation.
- List invoices: List invoices newest first. Filter by status, contact or issue date, search the number, reference and notes, and sort by issue date, due date, number, total or status. The response carries the outstanding total for the filtered set.
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.