Create authorize

Starts a sign-in — the address you send a browser to, and the beginning of every OAuth and OpenID Connect flow.

POST /v1/iam/oauth/authorize

Addresshttps://api.hanzo.ai/v1/iam/oauth/authorize
MethodPOST
Operationpost_iam_oauth_authorize
AuthAuthorization: Bearer $HANZO_API_KEY

Starts a sign-in — the address you send a browser to, and the beginning of every OAuth and OpenID Connect flow.

If the person is ALREADY signed in here, it does not ask them again: it returns them to the application with a one-time code and they never see this page. Otherwise it shows the right way to sign in for the application they are signing in to, or hands off to another identity provider if that is what they pick.

A client can say what it wants with prompt: none means answer without any screen at all — with the code if a session exists, with an error if not, but never with a page; login means ask for the password again even if a session exists; select_account means let the person choose among the accounts signed in on this browser, or sign in to another. login_hint names which of those accounts the request is for.

It returns only to an address the application has registered. That check happens before anything else, so a request naming an unregistered address is refused where the person can see it rather than being bounced onwards.

Request

The document declares no body for POST /v1/iam/oauth/authorize. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask MCP's describe for post_iam_oauth_authorize, which answers from the running route.

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo iam oauth authorize create
import { Configuration, IamApi } from 'hanzoai';

const api = new IamApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postIamOauthAuthorize();
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).post_iam_oauth_authorize()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.IamAPI.PostIamOauthAuthorize(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::post_iam_oauth_authorize(&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).postIamOauthAuthorize();
curl -X POST https://api.hanzo.ai/v1/iam/oauth/authorize \
  -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?