Replace terms

Records that the signed-in caller accepted the terms and the acceptable use policy, at the versions named.

PUT /v1/iam/terms

Addresshttps://api.hanzo.ai/v1/iam/terms
MethodPUT
Operationput_iam_terms
AuthAuthorization: Bearer $HANZO_API_KEY

Records that the signed-in caller accepted the terms and the acceptable use policy, at the versions named. It is how a person who arrived by a social provider, whose account the callback already made, records the same acceptance a code sign-up records at creation. Only the caller's own row is reachable.

Request

5 fields, body application/json (required).

FieldInTypeRequiredDescription
Cookieheaderstring—
Authorizationheaderstring—
X-Forwarded-Forheaderstring—
aupbodystring—
termsbodystring—

Response

StatusBodyMeaning
200iam.Answerok
400iam.Answerbad request
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.putIamTerms({ aup: "<aup>", terms: "<terms>" });
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_terms(aup="<aup>", terms="<terms>")
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

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

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?