Hanzo
OpenapiBilling

Answers one page of the caller's own ledger, newest first: what moved, how…

Answers one page of the caller's own ledger, newest first: what moved, how much, when, and what it was tagged with.

GET /v1/billing/transactions

Addresshttps://api.hanzo.ai/v1/billing/transactions
MethodGET
Operationget_billing_transactions
AuthAuthorization: Bearer $HANZO_API_KEY

Answers one page of the caller's own ledger, newest first: what moved, how much, when, and what it was tagged with.

count is the size of the WHOLE history rather than of the page, which is how a reader knows there is more to ask for, and user echoes the wallet the page was read for — the same subject the spend gate debits, so a customer can see which account answered rather than guessing from their own token.

A named handler, not a closure, so zipdoc can lift this prose into the registry.

Request

3 fields.

FieldInTypeRequiredDescription
currencyquerystringCurrency filters to one currency.
limitquerystringLimit is the page size; absent or non-positive takes the default 100.
offsetquerystringOffset is how far into the history the page starts.

Response

StatusBodyMeaning
200Transactionsok

200 body — 12 fields.

FieldInTypeAlwaysDescription
countbodyinteger
transactionsbodyTransaction[]
transactions[].amountbodyinteger
transactions[].createdAtbodystring
transactions[].currencybodystring
transactions[].expiresAtbodystring
transactions[].idbodystring
transactions[].metadatabodyany
transactions[].notesbodystring
transactions[].tagsbodystring
transactions[].typebodystring
userbodystring

Failure carries the platform error shape — see Errors.

Examples

hanzo billing transactions

Billing API · All Hanzo APIs · Interactive reference

How is this guide?

On this page