Answers either question about who belongs where: which organizations one person… — GET /v1/iam/get-memberships
Answers either question about who belongs where: which organizations one person can act in, or who can act in one organization.
GET /v1/iam/get-memberships
| Address | https://api.hanzo.ai/v1/iam/get-memberships |
| Method | GET |
| Operation | get_iam_get-memberships |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Answers either question about who belongs where: which organizations one person can act in, or who can act in one organization.
Both are org-scoped: a non-SuperAdmin may ask about ITS OWN org's roster, or about a user whose home org is its own, and nothing else. The bound comes from the verified credential via authz.Scope, so a request parameter can never widen it — a membership row names who may act and spend in an org, so a cross-tenant read is a customer roster leak.
Request
2 fields.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
user | query | string | — | User is "<homeOrg>/<username>" — which organizations that identity may act in. |
org | query | string | — | Org is an organization — who may act in it. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | iam.Answer | ok |
400 | iam.Answer | bad request |
200 body — 8 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
code | body | string | — | |
data | body | object | — | |
data2 | body | object | — | |
data3 | body | object | — | |
msg | body | string | — | |
name | body | string | — | |
status | body | string | — | |
sub | body | string | — |
Failure carries the platform error shape — see Errors.
Examples
hanzo iam get-membershipsimport { Configuration, IamApi } from 'hanzoai';
const api = new IamApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getIamGet-memberships();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_get-memberships()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.IamAPI.GetIamGet-memberships(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::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_get-memberships(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.IamApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new IamApi(client).getIamGet-memberships();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/get-memberships \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches iam through the iam tool, which names its 75 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": "list__well_known_jwks"
}
}
}'How is this guide?