# Replace terms

URL: https://docs.hanzo.ai/docs/openapi/iam/put-iam-terms

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

`PUT /v1/iam/terms`

> [IAM →](https://docs.hanzo.ai/docs/openapi/iam) · [All API references →](https://docs.hanzo.ai/docs/openapi) · [Get started →](https://docs.hanzo.ai/docs/guides)

|               |                                        |
| ------------- | -------------------------------------- |
| **Address**   | `https://api.hanzo.ai/v1/iam/terms`    |
| **Method**    | `PUT`                                  |
| **Operation** | `put_iam_terms`                        |
| **Auth**      | `Authorization: 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).

| Field             | In     | Type   | Required | Description |
| ----------------- | ------ | ------ | -------- | ----------- |
| `Cookie`          | header | string | —        |             |
| `Authorization`   | header | string | —        |             |
| `X-Forwarded-For` | header | string | —        |             |
| `aup`             | body   | string | —        |             |
| `terms`           | body   | string | —        |             |

## Response

| Status    | Body            | Meaning     |
| --------- | --------------- | ----------- |
| `200`     | iam.Answer      | ok          |
| `400`     | iam.Answer      | bad request |
| `default` | problem-details | refused     |

`200` body — 8 fields.

| Field    | In   | Type   | Always | Description |
| -------- | ---- | ------ | ------ | ----------- |
| `code`   | body | string | —      |             |
| `data`   | body | any    | —      |             |
| `data2`  | body | any    | —      |             |
| `data3`  | body | any    | —      |             |
| `msg`    | body | string | —      |             |
| `name`   | body | string | —      |             |
| `status` | body | string | —      |             |
| `sub`    | body | string | —      |             |

Failure carries the platform error shape — see [Errors](https://docs.hanzo.ai/docs/errors).

## Examples

**CLI**

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

**SDK**

**.ts**

```ts
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>" });
```

**.py**

```python
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>")
```

**.go**

```go
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
}
```

**.rs**

```rust
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?;
```

**.java**

```java
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();
```

**HTTP**

```bash
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**

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:

```bash
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](https://docs.hanzo.ai/docs/openapi/iam) · [All Hanzo APIs](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)