Hanzo
Cloud MCPbooks

get_v1_books_transactions

ListTransactions returns the org's booked ledger as a single-line register, newest first: one row per voucher, with its date, description, vendor, category, source and amount in exact cents.

ListTransactions returns the org's booked ledger as a single-line register, newest first: one row per voucher, with its date, description, vendor, category, source and amount in exact cents. It is the double-entry ledger projected to the register a human reads, filterable by posting-time window, category and vendor. Strictly read-only — it restates the books, it never moves them.

Toolget_v1_books_transactions
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments6
OperationGET /v1/books/transactions
Productbooks

Arguments

FieldTypeRequiredDefaultValuesDescription
categorystringCategory filters to one COA account, named by number ("5300") or by category slug ("software").
fromstringFrom is the RFC3339 start of the posting-time window, inclusive.
limitintegerLimit caps how many rows come back; 200 when absent or not positive.
sandboxstringSandbox reads the org's SANDBOX ledger when it is exactly "true".
tostringTo is the RFC3339 end of the posting-time window, inclusive.
vendorstringVendor filters to rows whose vendor or description contains this text, case-insensitively.

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_transactions",
         "arguments": {
           "category": "<category>",
           "from": "<from>",
           "limit": 0,
           "sandbox": "<sandbox>",
           "to": "<to>",
           "vendor": "<vendor>"
         }
       }
     }'

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

OperationRouteProductSummary
get_v1_books_transactionsGET /v1/books/transactionsbooksReturns the org's booked ledger as a single-line register, newest first: one row per…

The same capability over plain HTTP is in the books API reference, on https://api.hanzo.ai.


All 755 tools · The door · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).

How is this guide?

On this page