Data catalog / social
Social data
List the members of a Slack channel you belong to, with name, email, title, timezone and admin status, using your own Slack session. 2 credits per call.
In short: RichAPI POST /slack_channel_members returns the members of a Slack channel with their names, emails, titles, timezones and admin status. It needs the workspace subdomain, the channel ID, and the caller's own Slack session: an xoxc- client token and an xoxd- cookie, so it only reaches channels that user can see. Optional: max_members and cache. Billing is 2 credits per call. Authentication is an x-api-key header.
Last updated October 6, 2026
Members of a Slack channel
POST /slack_channel_members lists the people in one Slack channel: name, email, title, timezone and whether they are an admin.
The endpoint reads Slack as you. It needs four things:
workspace, the subdomain (acmeforacme.slack.com)channel_id, the ID that starts withC, from the channel's details or its URLtoken, yourxoxc-client tokencookie, yourxoxd-session cookie
The token and cookie come from a browser where you are logged in to that workspace, so the endpoint only sees channels you can see.
What a channel export costs
2 credits per call. The rate is per call, not per member. Use max_members to cap how many members come back, and cache: true to accept cached data when you re-run the same channel.
Rate
| Endpoint | What it does | Credits | Billed |
|---|---|---|---|
/slack_channel_members |
Extract Slack channel members with names, emails, titles, timezones, admin status. | 2 | per call |
Rates are read from the live OpenAPI spec. Credits are prepaid and never expire, and the price of a credit depends on your package: see pricing.
Before you use it
- The token and cookie act as your Slack login. Treat them as passwords, keep them out of shared code and logs, and sign out of the browser session afterwards to invalidate them.
- Many community workspaces have rules about contacting members or exporting member lists. Read the community's code of conduct before you build a list from it.
- A workspace can hide members' email addresses. Expect some rows with a name and no email.
From a member list to outreach
Where a member's email is present, find their LinkedIn profile from the email, then enrich it with person enrichment to see their role and company. Check the address with the email verifier before you send.
Reference
| Name | Type | Required | Description |
|---|---|---|---|
channel_id | string | Yes | Slack channel ID (e.g. C0123456789) |
cookie | string | Yes | Your Slack xoxd- session cookie |
token | string | Yes | Your Slack xoxc- client token |
workspace | string | Yes | Slack workspace subdomain (e.g. acme for acme.slack.com) |
cache | boolean | No | Use cached data if available |
max_members | integer | No | Maximum number of members to return |
channel_idstring · Required- Slack channel ID (e.g. C0123456789)
cookiestring · Required- Your Slack xoxd- session cookie
tokenstring · Required- Your Slack xoxc- client token
workspacestring · Required- Slack workspace subdomain (e.g. acme for acme.slack.com)
cacheboolean · Optional- Use cached data if available
max_membersinteger · Optional- Maximum number of members to return
Request
Minimum required parameters for a social data call.
{
"workspace": "acme",
"channel_id": "C0123456789",
"token": "xoxc-your-client-token",
"cookie": "xoxd-your-session-cookie"
}See it in a workflow
Playbooks
Real patterns, recipes, and prompts other builders run on RichAPI
Developer Docs
Auth, request shape, and error handling
FAQ
