Answers one billing account's roster.
Answers one billing account's roster. commerce stores no roster — that is IAM's — so the only member it can name is the caller, and that is what comes…
GET /v1/billing/accounts/{id}/members
| Address | https://api.hanzo.ai/v1/billing/accounts/{id}/members |
| Method | GET |
| Operation | get_billing_accounts_by_id_members |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Answers one billing account's roster.
commerce stores no roster — that is IAM's — so the only member it can name is the caller, and that is what comes back. What it does enforce is that the account named in the path is the caller's own: a foreign id is 403, not an empty list, because "no members" and "not your account" are different answers.
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 | ID is the billing account id, which for this store is the org's own id. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | Holder[] | ok |
200 body — 5 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
[].addedAt | body | string | — | |
[].email | body | string | — | |
[].id | body | string | — | |
[].role | body | string | — | |
[].userId | body | string | — |
Failure carries the platform error shape — see Errors.
Examples
hanzo billing accounts members <id>import { Configuration, BillingApi } from 'hanzoai';
const api = new BillingApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getBillingAccountsByIdMembers({ 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_accounts_by_id_members(id='id')cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.BillingAPI.GetBillingAccountsByIdMembers(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_accounts_by_id_members(&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).getBillingAccountsByIdMembers();curl https://api.hanzo.ai/v1/billing/accounts/<id>/members \
-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?