Books · Exports

6 declared Exports actions with worked requests and responses.

Exports execution

Read the exact action guide for prerequisites, identifier discovery, supported input, effects, captured successful and refused responses, verification and recovery. Synthetic fixture results do not authorize a live mutation or establish a provider outcome.

List export datasets: Describe every dataset Books can export: its key, the route family and permission that serves it, the date parameters it takes, and every column with its type and meaning. The chart and journal datasets use the column names the importers read, so an export re-imports.
Export a ledger dataset: Rows of one ledger dataset: chart_of_accounts, tax_rates, periods, journals (from/to), trial_balance (asOf), profit_and_loss, cash_flow (from/to) or balance_sheet (asOf). Flat rows with account codes and names, decimal amounts in the base currency, the columns exports.datasets.list documents. The whole set, never paged.
Export contacts: Rows of the contacts dataset: every customer and supplier with details, defaults and status.
Export an invoice dataset: Rows of invoices, invoice_lines, invoice_payments, aged_receivables (asOf) or sales_by_customer (from/to), with stable documented columns.
Export a bill dataset: Rows of bills, bill_lines, bill_payments, aged_payables (asOf) or purchases_by_supplier (from/to), with stable documented columns.
Export a bank dataset: Rows of bank_accounts, bank_lines or bank_summary (from/to): the bank, card and cash records, movement and reconciliation state.

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.