# Search slack

URL: https://docs.hanzo.ai/docs/openapi/provider/post-provider-slack-search

> Answers a workspace question: POST /v1/provider/slack/search.

`POST /v1/provider/slack/search`

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

|               |                                                 |
| ------------- | ----------------------------------------------- |
| **Address**   | `https://api.hanzo.ai/v1/provider/slack/search` |
| **Method**    | `POST`                                          |
| **Operation** | `post_provider_slack_search`                    |
| **Auth**      | `Authorization: Bearer $HANZO_API_KEY`          |

Answers a workspace question: POST /v1/provider/slack/search.

Slack's search.messages wants a USER token for a person's own view of a
workspace; a bot token searches what the app can see. Whichever the install
granted, the token custodied for this org is the one sent.

## Request

3 fields, body `application/json` (required).

| Field   | In   | Type            | Required | Description                                                                                                  |
| ------- | ---- | --------------- | -------- | ------------------------------------------------------------------------------------------------------------ |
| `count` | body | integer (int64) | —        | Count bounds the page, 1-100.                                                                                |
| `page`  | body | integer (int64) | —        | Page is the 1-based page of results.                                                                         |
| `query` | body | string          | —        | Query is Slack's own search syntax — bare words, or in:#channel, from:@someone, before:2026-09-01, has:link. |

## Response

| Status    | Body                    | Meaning |
| --------- | ----------------------- | ------- |
| `200`     | provider.slackSearchOut | ok      |
| `default` | problem-details         | refused |

`200` body — 11 fields.

| Field                    | In   | Type                       | Always | Description                                                                              |
| ------------------------ | ---- | -------------------------- | ------ | ---------------------------------------------------------------------------------------- |
| `matches`                | body | provider.slackSearchHit\[] | —      | Matches are this page's hits, most relevant first.                                       |
| `matches[].channel`      | body | string                     | —      | Channel is the conversation ID the match sits in.                                        |
| `matches[].channel_name` | body | string                     | —      | ChannelName is that conversation's name, when Slack reports one.                         |
| `matches[].permalink`    | body | string                     | —      | Permalink addresses the message in a browser.                                            |
| `matches[].text`         | body | string                     | —      | Text is the matching message's text.                                                     |
| `matches[].ts`           | body | string                     | —      | TS is the message's exact Slack timestamp, the handle for replying to or reacting to it. |
| `matches[].user`         | body | string                     | —      | User is the author's Slack user ID.                                                      |
| `matches[].username`     | body | string                     | —      | Username is the author's display name, when Slack reports one.                           |
| `page`                   | body | integer (int64)            | —      | Page is the page these matches came from.                                                |
| `pages`                  | body | integer (int64)            | —      | Pages is how many pages the query has in total.                                          |
| `total`                  | body | integer (int64)            | —      | Total is how many messages matched, across every page.                                   |

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

## Examples

**CLI**

```bash
hanzo provider slack search
```

**SDK**

**.ts**

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

const api = new ProviderApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postProviderSlackSearch({ count: 0, page: 0 });
```

**.py**

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ProviderApi(client).post_provider_slack_search(count=0, page=0)
```

**.go**

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

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

**.rs**

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

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

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

**.java**

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

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

var result = new ProviderApi(client).postProviderSlackSearch();
```

**HTTP**

```bash
curl -X POST https://api.hanzo.ai/v1/provider/slack/search \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "count": 0,
       "page": 0
     }'
```

**MCP**

MCP reaches **provider** through the `provider` tool, which names its 38 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_connections"
         }
       }
     }'
```

---

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