# List allowlist

URL: https://docs.hanzo.ai/docs/openapi/transport/get-transport-allowlist

> Returns the caller org's access policy for one transport: whether DMs are pairing-gated, allowlisted or open, whether group channels are open, allowlisted or disabled, the config-managed DM and group allow entries, the senders approved through PAIRING (read-only here), and the org's named access groups.

`GET /v1/transport/allowlist`

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

|               |                                               |
| ------------- | --------------------------------------------- |
| **Address**   | `https://api.hanzo.ai/v1/transport/allowlist` |
| **Method**    | `GET`                                         |
| **Operation** | `get_transport_allowlist`                     |
| **Auth**      | `Authorization: Bearer $HANZO_API_KEY`        |

Returns the caller org's access policy for one transport: whether
DMs are pairing-gated, allowlisted or open, whether group channels are open,
allowlisted or disabled, the config-managed DM and group allow entries, the
senders approved through PAIRING (read-only here), and the org's named access
groups. An unknown transport is a 404. The entries name the people the org's
bots admit, so reading them is an org admin's, as editing them is.

## Request

1 field.

| Field       | In    | Type   | Required | Description                                                                                      |
| ----------- | ----- | ------ | -------- | ------------------------------------------------------------------------------------------------ |
| `transport` | query | string | —        | Transport is the transport to read: discord, github, linear, slack, teams, telegram or whatsapp. |

## Response

| Status    | Body                    | Meaning |
| --------- | ----------------------- | ------- |
| `200`     | transport.allowlistView | ok      |
| `default` | problem-details         | refused |

`200` body — 8 fields.

| Field              | In   | Type      | Always | Description                                                                                                             |
| ------------------ | ---- | --------- | ------ | ----------------------------------------------------------------------------------------------------------------------- |
| `accessGroups`     | body | object    | —      | AccessGroups is the org's named sender sets, as group name -> transport -> member entries, held once for the whole org. |
| `accessGroups.*`   | body | object    | —      |                                                                                                                         |
| `accessGroups.*.*` | body | string\[] | —      |                                                                                                                         |
| `dm`               | body | string\[] | —      | DM is the CONFIG-managed DM allow entries — the list PUT /v1/transport/allowlist owns and replaces wholesale.           |
| `dmPolicy`         | body | string    | —      | DMPolicy decides every inbound DIRECT message, defaulting to "pairing" when the org has never set one.                  |
| `group`            | body | string\[] | —      | Group is the CONFIG-managed group allow entries, consulted only while GroupPolicy is "allowlist".                       |
| `groupPolicy`      | body | string    | —      | GroupPolicy decides every inbound GROUP or THREAD message — a thread is a group surface — defaulting to "open".         |
| `paired`           | body | string\[] | —      | Paired is the senders admitted by PAIRING — the entries POST /v1/transport/pairing/approve minted, DM scope only.       |

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

## Examples

**CLI**

```bash
hanzo transport allowlist get
```

**SDK**

**.ts**

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

const api = new TransportApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getTransportAllowlist();
```

**.py**

```python
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import TransportApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = TransportApi(client).get_transport_allowlist()
```

**.go**

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

resp, _, err := client.TransportAPI.GetTransportAllowlist(context.Background()).Execute()
if err != nil {
	return err
}
```

**.rs**

```rust
use hanzo_client::apis::{configuration::Configuration, transport_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = transport_api::get_transport_allowlist(&cfg, Default::default()).await?;
```

**.java**

```java
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.TransportApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new TransportApi(client).getTransportAllowlist();
```

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 https://api.hanzo.ai/v1/transport/allowlist \
  -H "Authorization: Bearer $HANZO_API_KEY"
```

**MCP**

Tool `transport`, op `get_transport_allowlist` — POST the JSON-RPC envelope to `https://api.hanzo.ai/v1/mcp`.

```bash
curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "transport",
         "arguments": {
           "op": "get_transport_allowlist",
           "input": {}
         }
       }
     }'
```

---

[Transport API](https://docs.hanzo.ai/docs/openapi/transport) · [All Hanzo APIs](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)