Hanzo AIDocs
Sign inAPI key

Create accept

Joins the caller to an organization through an invitation, for a person who already has an account.

POST /v1/iam/invitations/accept

IAM → · All API references → · Get started →

Addresshttps://api.hanzo.ai/v1/iam/invitations/accept
MethodPOST
Operationpost_iam_invitations_accept
AuthAuthorization: Bearer $HANZO_API_KEY

Joins the caller to an organization through an invitation, for a person who already has an account. Signing up through the invitation is the other way in (signupHandler); this one spends the same seat under the same rules.

Only the caller joins, as a member and never more; the request names nobody else. An invitation pinned to an address admits only the account holding that address, and only with a code IAM sent to it for this join — the account's own verified flag is not enough, because a tenant's identity provider can set it. An invitation pinned to a phone number or a username admits no other org's account this way. Joining an org the caller already belongs to succeeds and spends nothing. Every refusal is recorded, and an account refused acceptLimit times in acceptWindow is refused before anything is looked at.

Request

7 fields, body application/json (required).

FieldInTypeRequiredDescription
Cookieheaderstring—
Authorizationheaderstring—
Sec-Fetch-Siteheaderstring—
Content-Typeheaderstring—
codebodystring—
emailCodebodystring—
ownerbodystring—

Response

StatusBodyMeaning
200iam.Answerok
400iam.Answerbad request
403iam.Answerforbidden
429iam.Answertoo many requests
502iam.Answerbad gateway
503iam.Answerservice unavailable
defaultproblem-detailsrefused

200 body — 8 fields.

FieldInTypeAlwaysDescription
codebodystring—
databodyany—
data2bodyany—
data3bodyany—
msgbodystring—
namebodystring—
statusbodystring—
subbodystring—

Failure carries the platform error shape — see Errors.

Examples

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.

import { Configuration, IamApi } from 'hanzoai';

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

resp, _, err := client.IamAPI.PostIamInvitationsAccept(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_invitations_accept(&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).postIamInvitationsAccept();
curl -X POST https://api.hanzo.ai/v1/iam/invitations/accept \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "code": "<code>",
       "emailCode": "<emailCode>"
     }'

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?
PreviousCreate delete membershipNextSend invitations