POST /slack_channel_members • Credits: 2 credits per call

Slack Channel Members returns the member list of one Slack channel. The response holds a data object with the channel ID, the workspace, a members array and a total count. Each member carries a user ID, a real name, a display name, an email and a title. Each member also carries a phone number, a status text, a timezone, an admin flag, an owner flag and an avatar URL. Each call costs 2 credits, whatever the number of members returned.

A Slack channel holds the people behind a community, a customer program or a partner program. Slack shows that list in the app, but Slack gives no export for it. Slack Channel Members reads the channel through the Slack Web API and returns the full member list as structured JSON. RichAPI calls two Slack methods for each request: conversations.members for the member IDs, and users.info for the profile of each member. One call covers one channel.

CAUTION: Slack Channel Members reads a private workspace, not a public page. You must supply your own Slack session credentials. RichAPI provides no Slack access of its own.

RichAPI holds no Slack credential and runs no Slack OAuth app. The caller supplies the Slack credentials in the request body of every call. Two separate authentications happen in one request.

RichAPI builds the outbound Slack request from your two values.

The x-api-key header authenticates you to RichAPI and pays the credits. The cookie and the token authenticate the call to Slack. A valid x-api-key with a stale Slack session returns 401. A valid Slack session with no RichAPI key returns 401 as well.

If Slack answers missing_scope or not_in_channel, RichAPI returns 403. If Slack answers invalid_auth, token_revoked or not_authed, RichAPI returns 401.

A Slack session expires. If a working request starts to return 401, repeat these steps and send the new values.

CAUTION: Set max_members in every request. The configured default value is 0, and the accepted range is 1 to 10000. A request without max_members returns 422.

Slack Channel Members accepts the channel ID and nothing else. The channel ID is the value that starts with C and holds capital letters and digits, for example C0123456789. To find the ID, open the channel in a browser. The address bar shows https://<workspace>.slack.com/archives/C0123456789. The last path segment is the channel ID.

A full channel URL in channel_id returns 422, because the value fails the channel pattern. A channelUrl field returns 400, because channelUrl is not an accepted parameter name.

The block below is an example response for a channel with two members. The field names and the structure are exact. The people, the workspace, the IDs and the timings are illustrative.

Every profile field except user_id reads from the Slack profile of the member. If Slack hides a field or the member left it empty, the field is null. If Slack refuses the profile of one member, the response still holds that member with user_id and null in every other field.

Slack Channel Members returns the whole member list in one response. The request accepts no cursor, and the response holds no cursor and no next page token. RichAPI walks the Slack cursor pagination inside the single call.

Use max_members to control the size of the response and the duration of the call. A large channel takes a long time, because RichAPI reads one Slack profile per member. Set the client timeout to 180 seconds. If the call passes the RichAPI time budget, the response is 504 and RichAPI charges no credit.

Community teams and developer relations teams run large Slack workspaces. The channel list holds the members, but Slack shows no titles, no emails and no timezones in one view. Slack Channel Members turns one channel into a table that you can sort and filter.

Two channels of 400 members each cost 4 credits in total, or $0.08 on the 1,000 and 5,000 credit packs.

Slack Channel Members returns names, email addresses, job titles, phone numbers, status text, timezones and avatar URLs for real people inside a private workspace. You supply the Slack session that reads that workspace, and you decide what happens to the data afterwards. You are responsible for lawful and compliant handling of the member records, and for the workspace rules that apply to your Slack account.

Slack Channel Members costs 2 credits per call. 1 credit costs $0.02 on the 1,000 and 5,000 credit packs, so one call costs $0.04 there. Larger packs cost less per credit. The price is per call. A channel with 5 members and a channel with 5,000 members both cost 2 credits.

CAUTION: A successful call to an empty channel costs 2 credits. The response then holds total_members of 0 and a meta.quality_warning value.

RichAPI charges no credit for an error response. An error carries one of these statuses: 400, 401, 402, 403, 404, 422, 429, 500, 502, 504. RichAPI charges 2 credits for every 200 response.

No. Slack Channel Members needs two values from a signed-in Slack browser session: the d cookie value and the xoxc- client token. RichAPI sends no password to Slack and stores no Slack login.

You must bring your own. RichAPI holds no shared Slack credential and runs no Slack OAuth app, so every call carries your cookie and your token. The call reads only the workspace and the channel that your own Slack account can open.

None. The endpoint uses a Slack browser session instead of an OAuth app, so no scope list applies. The call inherits the permissions of the signed-in Slack user, and that user must be a member of the channel.

No. The channel_id parameter accepts capital letters and digits only, for example C0123456789. A full URL returns 422, and a channelUrl field returns 400 with the list of accepted parameter names.

The email field reads from the Slack profile of the member. If the Slack profile holds no email that your session can read, the field is null. The member still appears in data.members with a user_id.

No. Slack Channel Members costs 2 credits per call, whatever the value of total_members. A channel with 5,000 members and a channel with 5 members both cost 2 credits.

RichAPI caches a member list for 15 minutes. The cache key covers the workspace, the channel_id and the max_members values. It does not cover your Slack credentials. To read the live channel instead, set cache to false.

No. The response holds no bot flag and no is_bot field. Slack counts an app or a bot as a channel member, so a bot can appear in data.members with a user_id and few other values.