List methods

Returns the sign-in methods one application actually has switched on, so a login screen can render the right buttons for it without you hard-coding a list that drifts the moment you add a provider.

GET /v1/iam/auth/methods

IAM → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/iam/auth/methods`
Method	`GET`
Operation	`get_iam_auth_methods`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Returns the sign-in methods one application actually has switched on, so a login screen can render the right buttons for it without you hard-coding a list that drifts the moment you add a provider.

Public by design: it is read before anyone has signed in, and it exposes only which methods exist, never their credentials.

Request

1 field.

Field	In	Type	Required	Description
`clientId`	query	string	—	ClientId is the application's OAuth client id.

Response

Status	Body	Meaning
`200`	iam.Answer	ok
`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 auth methods

.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.getIamAuthMethods();

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_auth_methods()

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

resp, _, err := client.IamAPI.GetIamAuthMethods(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_auth_methods(&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).getIamAuthMethods();

curl https://api.hanzo.ai/v1/iam/auth/methods \
  -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 application NextGet certs