Hanzo
OpenapiBooks

Pulls every connected bank (Plaid/Teller) for the caller's org, maps each…

Pulls every connected bank (Plaid/Teller) for the caller's org, maps each fetched transaction to a posting and books it idempotently, then advances that…

POST /v1/books/bank/sync

Addresshttps://api.hanzo.ai/v1/books/bank/sync
MethodPOST
Operationpost_books_bank_sync
AuthAuthorization: Bearer $HANZO_API_KEY

Pulls every connected bank (Plaid/Teller) for the caller's org, maps each fetched transaction to a posting and books it idempotently, then advances that connector's cursor so the next sync resumes where this one stopped. One connector's outage is skipped rather than failing the whole sync. It reports the batch: how many transactions were seen, how many vouchers posted, how many inflows reconciled against the processor clearing account, how many raised a question, how many were own-account transfers, and how many were already-processed no-ops. It is READ-ONLY against the bank — it ingests, it never sends money.

Request

The document declares no body for POST /v1/books/bank/sync. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask the MCP door's describe for post_books_bank_sync, which answers from the running route.

Response

StatusBodyMeaning
200BankTallyok

200 body — 6 fields.

FieldInTypeAlwaysDescription
ingestedbodyintegertransactions seen
postedbodyintegervouchers newly posted (outflow + reconciled)
questionsbodyintegerunmatched inflows that raised a question
reconciledbodyintegerinflows cleared against Square-clearing
skippedbodyintegeralready-processed idempotent no-ops
transfersbodyintegerown-account moves recorded (no P&L)

Failure carries the platform error shape — see Errors.

Examples

hanzo books bank sync

Books API · All Hanzo APIs · Interactive reference

How is this guide?

On this page