Replace invitations

Changes an invitation's terms — the role it grants, how many may redeem it, or when it expires.

PUT /v1/iam/invitations/{owner}/{name}

Addresshttps://api.hanzo.ai/v1/iam/invitations/{owner}/{name}
MethodPUT
Operationput_iam_invitations_by_owner_by_name
AuthAuthorization: Bearer $HANZO_API_KEY

Changes an invitation's terms — the role it grants, how many may redeem it, or when it expires. What it is called does not change.

Request

18 fields, body application/json (required).

FieldInTypeRequiredDescription
ownerpathstringyes
namepathstringyes
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 owner set <owner> <name>
import { Configuration, IamApi } from 'hanzoai';

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

resp, _, err := client.IamAPI.PutIamInvitationsByOwnerByName(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::put_iam_invitations_by_owner_by_name(&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).putIamInvitationsByOwnerByName();
curl -X PUT https://api.hanzo.ai/v1/iam/invitations/<owner>/<name> \
  -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?