# Create members URL: https://docs.hanzo.ai/docs/openapi/team/post-team-rooms-by-id-members > Adds people to a room and answers the room as it now stands. `POST /v1/team/rooms/{id}/members` > [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}/members` | | **Method** | `POST` | | **Operation** | `post_team_rooms_by_id_members` | | **Auth** | `Authorization: Bearer $HANZO_API_KEY` | Adds people to a room and answers the room as it now stands. Anyone in the space except a guest may join a public channel by naming themselves. Adding somebody else takes being in the room already (or administering the space, for a room they can see). A direct message's people are what it is, so none can be added — open another one. Everyone added must be a member of the space or one of the org's agents; an agent added to a room answers when it is @-mentioned there. ## Request 4 fields, body `application/json` (required). | Field | In | Type | Required | Description | | --------- | ---- | --------- | -------- | --------------------------------------------------------------------- | | `id` | path | string | yes | ID is the room, from the path. | | `id` | body | string | — | ID is the room, from the path. | | `members` | body | string\[] | — | Members are the account uuids to add — people or agents of the space. | | `space` | body | string | — | Space is the space uuid holding it. | ## 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** `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, TeamApi } from 'hanzoai'; const api = new TeamApi(new Configuration({ accessToken: process.env.HANZO_API_KEY })); const { data } = await api.postTeamRoomsByIdMembers({ id: 'id', id: "", members: [""] }); ``` **.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).post_team_rooms_by_id_members(id='id', id="", members=[""]) ``` **.go** ```go cfg := hanzoai.NewConfiguration() cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY")) client := hanzoai.NewAPIClient(cfg) resp, _, err := client.TeamAPI.PostTeamRoomsByIdMembers(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::post_team_rooms_by_id_members(&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).postTeamRoomsByIdMembers(); ``` **HTTP** ```bash curl -X POST https://api.hanzo.ai/v1/team/rooms//members \ -H "Authorization: Bearer $HANZO_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "id": "", "members": [ "" ] }' ``` **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)