# Create members

URL: https://docs.hanzo.ai/docs/openapi/team/post-team-channels-by-id-members

> Adds people to a channel and answers the channel as it now stands.

`POST /v1/team/channels/{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/channels/{id}/members` |
| **Method**    | `POST`                                               |
| **Operation** | `post_team_channels_by_id_members`                   |
| **Auth**      | `Authorization: Bearer $HANZO_API_KEY`               |

Adds people to a channel and answers the channel 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 channel already (or
administering the space, for a channel 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 channel
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 channel, from the path.                                     |
| `id`      | body | string    | —        | ID is the channel, 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.teamChannelOne | ok      |
| `default` | problem-details     | refused |

`200` body — 12 fields.

| Field              | In   | Type             | Always | Description                                                                                                                                                                                                                       |
| ------------------ | ---- | ---------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `channel`          | body | team.teamChannel | —      |                                                                                                                                                                                                                                   |
| `channel.archived` | body | boolean          | —      | Archived reports that the channel has been closed.                                                                                                                                                                                |
| `channel.bindings` | body | string\[]        | —      | Bindings are what this channel is ABOUT, each a "\<kind>:\<ref>" string — "project:acme/web", "repo:hanzoai/cloud", "issue:1010".                                                                                                 |
| `channel.direct`   | body | boolean          | —      | Direct reports that this is a channel between people rather than a named channel.                                                                                                                                                 |
| `channel.id`       | body | string           | —      | ID is the channel document's own id, and the value the bind op addresses.                                                                                                                                                         |
| `channel.kind`     | body | string           | —      | Kind is what sort of channel this is: "public" (open to everyone in the space), "private" (open to its members) or "dm" (a conversation between the people in it).                                                                |
| `channel.life`     | body | string           | —      | Life is the channel's lifecycle INTENT — "standing" or "bound" (HIP-0523 §2).                                                                                                                                                     |
| `channel.members`  | body | string\[]        | —      | Members are the account uuids in the channel, 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 channels an agent is in. |
| `channel.name`     | body | string           | —      | Name is what a person sees in a sidebar.                                                                                                                                                                                          |
| `channel.private`  | body | boolean          | —      | Private reports that the channel is restricted to its members.                                                                                                                                                                    |
| `channel.space`    | body | string           | —      | Space is the space uuid holding this channel.                                                                                                                                                                                     |
| `channel.topic`    | body | string           | —      | Topic is the channel'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 channels members create <id>
```

**SDK**

**.ts**

```ts
import { Configuration, TeamApi } from 'hanzoai';

const api = new TeamApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postTeamChannelsByIdMembers({ id: 'id', id: "<id>", members: ["<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_channels_by_id_members(id='id', id="<id>", members=["<members>"])
```

**.go**

```go
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.TeamAPI.PostTeamChannelsByIdMembers(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_channels_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).postTeamChannelsByIdMembers();
```

The method above is the one at the current release of the document. `hanzoai@8.5.914` (npm) and `hanzoai@8.5.914` (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. [SDKs →](https://docs.hanzo.ai/docs/sdks)

**HTTP**

```bash
curl -X POST https://api.hanzo.ai/v1/team/channels/<id>/members \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "id": "<id>",
       "members": [
         "<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)
