Create invitations

Issues an invitation to join your organization — the code or link a new member redeems, with the role they arrive holding and the date it stops working.

POST /v1/iam/invitations

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

Issues an invitation to join your organization — the code or link a new member redeems, with the role they arrive holding and the date it stops working. A name already used in the organization is refused.

Request

16 fields, body application/json (required).

FieldInTypeRequiredDescription
applicationbodystring—
codebodystring—
createdTimebodystring—
defaultCodebodystring—
displayNamebodystring—
emailbodystring—
isRegexpbodyboolean—
namebodystring—
ownerbodystring—
phonebodystring—
quotabodyinteger (int64)—
signupGroupbodystring—
statebodystring—
updatedTimebodystring—
usedCountbodyinteger (int64)—
usernamebodystring—

Response

StatusBodyMeaning
200iam.Invitationok
202Approvalheld for approval
defaultproblem-detailsrefused

200 body — 22 fields.

FieldInTypeAlwaysDescription
applicationbodystring—
codebodystring—
createdAtbodystring (date-time)—
createdTimebodystring—
defaultCodebodystring—
deletedbodyboolean—
displayNamebodystring—
emailbodystring—
generatedbodyboolean—Generated reports that IAM minted Code itself, from crypto/rand, when the invitation was created.
idbodystring—
isRegexpbodyboolean—
namebodystring—
ownerbodystring—
phonebodystring—
quotabodyinteger (int64)—
sentTimebodystring—SentTime is when an email about this invitation last went to its pinned address (RFC 3339), "" when none has.
signupGroupbodystring—
statebodystring—
updatedAtbodystring (date-time)—
updatedTimebodystring—
usedCountbodyinteger (int64)—
usernamebodystring—

Failure carries the platform error shape — see Errors.

Examples

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

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

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

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?