get_v1_books_export
ExportPackage returns the complete financial package for the caller's org over (from, to]: the trial balance, the P&L, the balance sheet, and the GL detail behind them — the four statements a tax…
ExportPackage returns the complete financial package for the caller's org over (from, to]: the trial balance, the P&L, the balance sheet, and the GL detail behind them — the four statements a tax preparer or an investor asks for, assembled from the one ledger in a single read so they cannot disagree with each other.
| Tool | get_v1_books_export |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 5 |
| Operation | GET /v1/books/export |
| Product | books |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
format | string | — | — | — | Format is the export encoding. Only "json" is supported; empty means json. |
from | string | — | — | — | From is the RFC3339 start of the window, exclusive. Empty means all time. |
limit | integer | — | — | — | Limit caps the GL detail rows included as the audit trail; 5000 when absent or not positive. |
sandbox | string | — | — | — | Sandbox reads the org's SANDBOX ledger when it is exactly "true". |
to | string | — | — | — | To is the RFC3339 end of the window, inclusive. Empty means up to now. |
tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_v1_books_export",
"arguments": {
"format": "<format>",
"from": "<from>",
"limit": 0,
"sandbox": "<sandbox>",
"to": "<to>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. limit holds a stand-in that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so that value is this page's, not the API's. Neither the door nor the operation declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
cloud_get_v1_books_export | GET /v1/books/export | books | ExportPackage returns the complete financial package for the caller's org over (from,… |
The same capability over plain HTTP is in the books API reference, on https://api.hanzo.ai.
All 833 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?