List identities

GET /v1/network/identities

Network → · All API references → · Get started →


Address	`https://api.hanzo.ai/v1/network/identities`
Method	`GET`
Operation	`get_network_identities`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Returns the fabric identities the caller's org owns.

One row per identity tagged with the org's "org-<org>" role attribute, each naming the IAM subject it logs in as.

A tenancy read over the full inventory, so like the mesh list it does NOT degrade: an unconfigured deployment answers 503.

Request

GET /v1/network/identities takes no parameters and no body — the credential is the whole request.

Response

Status	Body	Meaning
`200`	network.identityList	ok
`default`	problem-details	refused

200 body — 5 fields.

Field	In	Type	Always	Description
`identities`	body	network.identityView[]	—	Identities is one row per fabric identity tagged with the caller's org role.
`identities[].externalId`	body	string	—	ExternalID is the IAM subject the identity logs in as: the controller admits a bearer whose `sub` equals it.
`identities[].id`	body	string	—	ID is the identity's fabric id — the key DELETE addresses.
`identities[].name`	body	string	—	Name is the identity's name within the org.
`identities[].roles`	body	string[]	—	Roles are the identity's role attributes as the fabric holds them: the "org-<org>" of every org it was ensured in, plus any org-scoped roles.

Failure carries the platform error shape — see Errors.

Examples

hanzo network identities list

import { Configuration, NetworkApi } from 'hanzoai';

const api = new NetworkApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getNetworkIdentities();

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = NetworkApi(client).get_network_identities()

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

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

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

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

let result = network_api::get_network_identities(&cfg, Default::default()).await?;

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

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

var result = new NetworkApi(client).getNetworkIdentities();

The method above is the one at the current release of the document. [email protected] (npm) was 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/network/identities \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches network through the zt tool, which names its 4 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_mesh_services"
         }
       }
     }'

Network API · All Hanzo APIs · Interactive reference

Request

Response

Examples

On this page