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
| Address | https://api.hanzo.ai/v1/billing/transactions |
| Method | GET |
| Operation | get_billing_transactions |
| Auth | Authorization: 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.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
currency | query | string | — | Currency filters to one currency. |
limit | query | string | — | Limit is the page size; absent or non-positive takes the default 100. |
offset | query | string | — | Offset is how far into the history the page starts. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | Transactions | ok |
200 body — 12 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
count | body | integer | — | |
transactions | body | Transaction[] | — | |
transactions[].amount | body | integer | — | |
transactions[].createdAt | body | string | — | |
transactions[].currency | body | string | — | |
transactions[].expiresAt | body | string | — | |
transactions[].id | body | string | — | |
transactions[].metadata | body | any | — | |
transactions[].notes | body | string | — | |
transactions[].tags | body | string | — | |
transactions[].type | body | string | — | |
user | body | string | — |
Failure carries the platform error shape — see Errors.
Examples
hanzo billing transactionsimport { Configuration, BillingApi } from 'hanzoai';
const api = new BillingApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getBillingTransactions();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import BillingApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = BillingApi(client).get_billing_transactions()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.BillingAPI.GetBillingTransactions(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, billing_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = billing_api::get_billing_transactions(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.BillingApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new BillingApi(client).getBillingTransactions();curl https://api.hanzo.ai/v1/billing/transactions \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches billing through the billing tool, which names its 9 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "get_billing_balance"
}
}
}'How is this guide?