Hanzo
OpenapiBooks

Finish connecting a bank account (not yet available)

ANSWERS 501 UNCONDITIONALLY. It is the intended second hop of the bank-linking handshake — trade the provider's short-lived public token for the durable…

POST /v1/books/bank/exchange

Addresshttps://api.hanzo.ai/v1/books/bank/exchange
MethodPOST
Operationpost_books_bank_exchange
AuthAuthorization: Bearer $HANZO_API_KEY

ANSWERS 501 UNCONDITIONALLY. It is the intended second hop of the bank-linking handshake — trade the provider's short-lived public token for the durable access credential and seal that credential into KMS — and nothing on the HTTP path reaches an implementation today.

The durable bank credential is the reason this hop exists: it is meant to be sealed server-side and never handed back to the caller. Since the route never succeeds, no credential is stored by it and no bank is connected through it.

Documented as refusing rather than declared with a success body, for the same reason as the first hop: it has never sent one, and stating a shape it has never produced would put a return type in every SDK for a call that always fails. A caller with no principal gets 401 before the 501.

Request

The document declares no body for POST /v1/books/bank/exchange. 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_exchange, which answers from the running route.

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo books bank exchange

Books API · All Hanzo APIs · Interactive reference

How is this guide?

On this page