List service accounts

Returns your organization's service accounts — what each is called and when it was created.

GET /v1/iam/service-accounts

IAM → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/iam/service-accounts`
Method	`GET`
Operation	`get_iam_service-accounts`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Returns your organization's service accounts — what each is called and when it was created. Never their secrets: a key's secret half exists in a response exactly once, when it is minted. Paginated in memory over the already org-scoped slice — the set per org is small, so a dedicated count query is overkill (v1 service_account.go:296-307).

Request

3 fields.

Field	In	Type	Required	Description
`organization`	query	string	—	Organization is the organization whose service accounts to list.
`p`	query	integer	—	P is the 1-indexed page to return.
`pageSize`	query	integer	—	Size is how many accounts a page holds.

Response

Status	Body	Meaning
`200`	iam.Answer	ok
`202`	Approval	held for approval
`400`	iam.Answer	bad request
`default`	problem-details	refused

200 body — 8 fields.

Field	In	Type	Always
`code`	body	string	—
`data`	body	any	—
`data2`	body	any	—
`data3`	body	any	—
`msg`	body	string	—
`name`	body	string	—
`status`	body	string	—
`sub`	body	string	—

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo iam service-accounts list

.ts

.py

.go

.rs

.java

import { Configuration, IamApi } from 'hanzoai';

const api = new IamApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getIamService-accounts();

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import IamApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = IamApi(client).get_iam_service-accounts()

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

resp, _, err := client.IamAPI.GetIamService-accounts(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, iam_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = iam_api::get_iam_service-accounts(&cfg, Default::default()).await?;

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

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

var result = new IamApi(client).getIamService-accounts();

The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →

curl https://api.hanzo.ai/v1/iam/service-accounts \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches iam through the iam tool, which names its 44 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": "list_iam_applications"
         }
       }
     }'

IAM API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList Users — GET /v1/iam/scim/v2/Users NextGet teams