Get transactions

Reads one ledger entry by its id. It is the MEMBER of the collection beside it rather than a second way to ask — the same rows GET…

GET /v1/billing/transactions/{id}

Billing → · All API references → · Get started →


Address	`https://api.hanzo.ai/v1/billing/transactions/{id}`
Method	`GET`
Operation	`get_billing_transactions_by_id`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Reads one ledger entry by its id.

It is the MEMBER of the collection beside it rather than a second way to ask — the same rows GET /v1/billing/transactions lists, addressed one at a time. A top-up receipt is read here, because a receipt IS a ledger entry: the id this takes is the transactionId a top-up hands back.

The read is narrower than the list: commerce's core loads the row and refuses anything that is not a deposit, so a row that exists but is not a top-up answers 404. That asymmetry is stated rather than closed, because widening a money read to make two shapes match is not a change worth making for symmetry.

The books are the caller's own and cannot be named, so a guessed id misses rather than reaching another tenant's ledger.

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

Request

1 field.

Field	In	Type	Required	Description
`id`	path	string	yes

Response

Status	Body	Meaning
`200`	billing.Transaction	ok
`default`	problem-details	refused

200 body — 9 fields.

Field	In	Type	Always
`amount`	body	integer (int64)	—
`createdAt`	body	string	—
`currency`	body	string	—
`expiresAt`	body	string	—
`id`	body	string	—
`metadata`	body	any	—
`notes`	body	string	—
`tags`	body	string	—
`type`	body	string	—

Failure carries the platform error shape — see Errors.

Examples

hanzo billing transactions get <id>

import { Configuration, BillingApi } from 'hanzoai';

const api = new BillingApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getBillingTransactionsById({ id: 'id' });

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_by_id(id='id')

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.BillingAPI.GetBillingTransactionsById(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::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_by_id(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.BillingApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new BillingApi(client).getBillingTransactionsById();

curl https://api.hanzo.ai/v1/billing/transactions/<id> \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches billing through the billing tool, which names its 9 operations with its own verbs — this one among them, under a name only MCP 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"
         }
       }
     }'

Billing API · All Hanzo APIs · Interactive reference

Request

Response

Examples

On this page