# Replace rooms URL: https://docs.hanzo.ai/docs/openapi/team/put-team-rooms-by-id > States what a room is for: its lifecycle intent, and what it is about. `PUT /v1/team/rooms/{id}` > [Team →](https://docs.hanzo.ai/docs/openapi/team) · [All API references →](https://docs.hanzo.ai/docs/openapi) · [Get started →](https://docs.hanzo.ai/docs/guides) | | | | ------------- | ----------------------------------------- | | **Address** | `https://api.hanzo.ai/v1/team/rooms/{id}` | | **Method** | `PUT` | | **Operation** | `put_team_rooms_by_id` | | **Auth** | `Authorization: Bearer $HANZO_API_KEY` | States what a room is for: its lifecycle intent, and what it is about. It answers the room as it now stands. The write is a platform MIXIN on the room document, applied through the SAME applyTx path the Team client's own writes take and broadcast to every connected client — so a room bound here updates live in an open space rather than on the next reload. A team member binds a room they can see; an application of the org binds its public channels only; anybody else without a team session is 401. ## Request 5 fields, body `application/json` (required). | Field | In | Type | Required | Description | | ---------- | ---- | --------- | -------- | ------------------------------------------------------ | | `id` | path | string | yes | ID is the room to bind, from the path. | | `bindings` | body | string\[] | — | Bindings REPLACES what the room is about, wholly. | | `id` | body | string | — | ID is the room to bind, from the path. | | `life` | body | string | — | Life sets the lifecycle intent: "standing" or "bound". | | `space` | body | string | — | Space names the space holding the room. | ## Response | Status | Body | Meaning | | --------- | --------------- | ------- | | `200` | team.teamRoom | ok | | `default` | problem-details | refused | `200` body — 11 fields. | Field | In | Type | Always | Description | | ---------- | ---- | --------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `archived` | body | boolean | — | Archived reports that the room has been closed. | | `bindings` | body | string\[] | — | Bindings are what this room is ABOUT, each a "\:\" string — "project:acme/web", "repo:hanzoai/cloud", "issue:1010". | | `direct` | body | boolean | — | Direct reports that this is a room between people rather than a named room. | | `id` | body | string | — | ID is the room document's own id, and the value the bind op addresses. | | `kind` | body | string | — | Kind is what sort of room this is: "channel" (open to everyone in the space), "private" (open to its members) or "dm" (a conversation between the people in it). | | `life` | body | string | — | Life is the room's lifecycle INTENT — "standing" or "bound" (HIP-0523 §2). | | `members` | body | string\[] | — | Members are the account uuids in the room, agents included: an agent projects as a space member under a uuid derived from its id, so a caller comparing this against GET /v1/bot/members learns which rooms an agent is in. | | `name` | body | string | — | Name is what a person sees in a sidebar. | | `private` | body | boolean | — | Private reports that the room is restricted to its members. | | `space` | body | string | — | Space is the space uuid holding this room. | | `topic` | body | string | — | Topic is the room's own one-line subject, as the Team client sets it. | Failure carries the platform error shape — see [Errors](https://docs.hanzo.ai/docs/errors). ## Examples **CLI** ```bash hanzo team rooms set ``` **SDK** **.ts** ```ts import { Configuration, TeamApi } from 'hanzoai'; const api = new TeamApi(new Configuration({ accessToken: process.env.HANZO_API_KEY })); const { data } = await api.putTeamRoomsById({ id: 'id', bindings: [""], id: "" }); ``` **.py** ```python from hanzoai.cloud import ApiClient, Configuration from hanzoai.cloud.api import TeamApi client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"])) result = TeamApi(client).put_team_rooms_by_id(id='id', bindings=[""], id="") ``` **.go** ```go cfg := hanzoai.NewConfiguration() cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY")) client := hanzoai.NewAPIClient(cfg) resp, _, err := client.TeamAPI.PutTeamRoomsById(context.Background()).Execute() if err != nil { return err } ``` **.rs** ```rust use hanzo_client::apis::{configuration::Configuration, team_api}; let mut cfg = Configuration::new(); cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok(); let result = team_api::put_team_rooms_by_id(&cfg, Default::default()).await?; ``` **.java** ```java import ai.hanzo.cloud.ApiClient; import ai.hanzo.cloud.api.TeamApi; ApiClient client = new ApiClient(); client.setBearerToken(System.getenv("HANZO_API_KEY")); var result = new TeamApi(client).putTeamRoomsById(); ``` **HTTP** ```bash curl -X PUT https://api.hanzo.ai/v1/team/rooms/ \ -H "Authorization: Bearer $HANZO_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "bindings": [ "" ], "id": "" }' ``` **MCP** MCP reaches **team** through the `team` tool, which names its 33 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_team_account_providers" } } }' ``` --- [Team API](https://docs.hanzo.ai/docs/openapi/team) · [All Hanzo APIs](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)