Don't have a paid plan? Join the Developer Program and provision a fully-featured sandbox for free.
Facts
application/x-www-form-urlencoded Arguments
Required arguments
tokenstringRequiredAuthentication token bearing required scopes. Tokens should be passed as an HTTP Authorization header or alternatively, as a POST parameter.
xxxx-xxxxxxxxx-xxxxOptional arguments
dateOptionalThe day to report on, as YYYY-MM-DD in UTC. Each metric counts that day's activity. Defaults to the most recent day with data. The response's available_date_range gives the earliest and latest days you can request.
2026-09-30team_idstringOptionalWorkspace ID to scope the results to. With an organization-level token, omit it for organization-wide results. A workspace-level token may only pass its own workspace.
T1234567890member_typesarrayOptionalComma-separated list of member types to include. Omit to include every member type.
9regular_members single_channel_guests multi_channel_guests frontline_members org_owners org_admins workspace_owners workspace_admins invitedsingle_channel_guests,multi_channel_guestsuser_idsarrayOptionalComma-separated list of user IDs to return. Use admin.analytics.members.metadata, which supports searching by name and email, to find them; this method never returns names or email addresses. Up to 500 IDs. Deactivated members may be included. Omit to return every member.
500U0123ABCD,U0456EFGHcursorstringOptionalPaginate through collections of data by setting the cursor parameter to a next_cursor attribute returned by a previous request's response_metadata. Default value fetches the first "page" of the collection.
Y3Vyc29yX21hcms6QW9JSUtqWTA=limitintegerOptionalMaximum number of members to return. Max allowed is 500.
100Usage info
This method returns, as JSON, the same per-member metrics as the member analytics dashboard for a single day: whether the member was active, messages posted, reactions, files, huddles, searches, and canvas, list, clip, workflow, app, and AI usage. It replaces the member type of the admin.analytics.getFile method, which also returns a daily file. To build a history, call it once per day; to backfill, call it once for each past day.
Results are sorted by user ID and paginated with the cursor parameter. The response identifies members by ID only and carries no names, email addresses, or other profile fields; the admin.analytics.members.metadata method returns those, and supports searching by name and email. To combine the two, join on the user_id response field: list or search members with the admin.analytics.members.metadata method and pass each page's IDs here as the user_ids parameter. Pages of the two methods are not interchangeable, because the admin.analytics.members.metadata method has no activity date and so can include members this method leaves out.
Choosing a date
If you omit the date parameter, the response covers the most recent day with data. Every response says which day it covers in the date response field and which days have data in the available_date_range response field, so a client can call once without the date parameter to learn the supported days before backfilling, and each day to learn whether a new day has landed. Data for a day is usually available early the following day, UTC. The method reports one day at a time; the count response fields, such as active_day_count and message_count, keep the dashboard's names so that a date range can be added later without changing the response.
Metrics
Every metric the plan and the token include is present on every row; a member with no activity on that day has 0 for each, and the active_day_count response field is 0 or 1. Which metrics a row carries follows the token's team, not the team_id parameter: AI metrics need a paid or Slack AI plan and are not returned to an enterprise workspace token (use an organization-level token with the team_id parameter to scope instead), and the canvas, list, clip, Slackbot skill, and app metrics are only returned for organization-level requests.
This method replaces the member file from the admin.analytics.getFile method, and some of that file's fields are renamed, moved, or dropped. Five of the is_active* boolean fields become *_day_count integer response fields, which are 0 or 1 for a single day:
getFile field | Replacement |
|---|---|
messages_posted_count | message_count |
channel_messages_posted_count | channel_message_count |
reactions_added_count | reaction_count |
is_active | active_day_count |
is_active_desktop | active_on_desktop_day_count |
is_active_android | active_on_android_day_count |
is_active_ios | active_on_ios_day_count |
is_active_slack_connect | active_on_slack_connect_day_count |
is_active_apps | No boolean; use messages_read_from_apps_count, actions_taken_with_apps_count, and automations_executed_with_apps_count |
is_active_workflows | No boolean; use workflow_run_count |
is_guest | account_type, is_restricted, and is_ultra_restricted |
email_address | email in the admin.analytics.members.metadata method |
enterprise_employee_number | employee_number in the admin.analytics.members.metadata method |
total_calls_count, slack_calls_count, is_billable_seat | Not returned |
The files_added_count, slack_huddles_count, search_count, date_claimed, user_id, and enterprise_id response fields keep their getFile names.
For a member who has never signed in, or never been active on a platform, the date_claimed response field and the matching date_last_active* response field are omitted rather than sent as 0. A date parameter outside the range in the available_date_range response field returns data_not_available_for_date. When there are no more pages, the response_metadata response field is omitted.
Response
A page of members, sorted by user ID, with their activity metrics for the day.
{
"ok": true,
"date": "2026-09-30",
"available_date_range": {
"start_date": "2025-11-01",
"end_date": "2026-09-30"
},
"members": [
{
"user_id": "U0123ABCD",
"team_id": "E0123ABCD",
"enterprise_id": "E0123ABCD",
"date_created": 1600000000,
"account_type": "member",
"is_admin": false,
"is_owner": false,
"is_primary_owner": false,
"is_restricted": false,
"is_ultra_restricted": false,
"date_last_active": 1760054400,
"active_day_count": 1,
"message_count": 14,
"reaction_count": 3,
"ai_usage_count": 2
}
],
"total_count": 1250,
"response_metadata": {
"next_cursor": "Y3Vyc29yX21hcms6QW9JSUtqWTA="
}
}
Typical error response
{
"ok": false,
"error": "data_not_available_for_date"
}
Errors
This table lists the expected errors that this method could return. However, other errors can be returned in the case where the service is down or other unexpected factors affect processing. Callers should always check the value of the ok parameter in the response.
access_deniedAccess to a resource specified in the request is denied.
accesslimitedAccess to this method is limited on the current network
account_inactiveAuthentication token is for a deleted user or workspace when using a bot token.
admin_analytics_disabledAnalytics are temporarily unavailable. Wait and try again.
analytics_unavailableAnalytics could not be found for the team.
data_not_available_for_dateAnalytics are not available for date. Call the method without date and use available_date_range from the response to find the supported days.
date_before_created_datedate is before the team or organization was created.
deprecated_endpointThe endpoint has been deprecated.
ekm_access_deniedAdministrators have suspended the ability to post a message.
enterprise_is_restrictedThe method cannot be called from an Enterprise.
fatal_errorThe server could not complete your operation(s) without encountering a catastrophic error. It's possible some aspect of the operation succeeded before the error was raised.
feature_not_availableThe team's plan does not include analytics API access.
incomplete_analyticsThe full set of results could not be retrieved. Wait and try again.
internal_errorThe server could not complete your operation(s) without encountering an error, likely due to a transient issue on our end. It's possible some aspect of the operation succeeded before the error was raised.
invalid_arg_nameThe method was passed an argument whose name falls outside the bounds of accepted or expected values. This includes very long names and names with non-alphanumeric characters other than _. If you get this error, it is typically an indication that you have made a very malformed API call.
invalid_argumentsRequired arguments either were not provided or contain invalid values, including a date that is not a real calendar day.
invalid_array_argThe method was passed an array as an argument. Please only input valid strings.
invalid_authSome aspect of authentication cannot be validated. Either the provided token is invalid or the request originates from an IP address disallowed from making the request.
invalid_charsetThe method was called via a POST request, but the charset specified in the Content-Type header was invalid. Valid charset names are: utf-8 iso-8859-1.
invalid_cursorThe cursor value is not valid.
invalid_form_dataThe method was called via a POST request with Content-Type application/x-www-form-urlencoded or multipart/form-data, but the form data was either missing or syntactically invalid.
invalid_post_typeThe method was called via a POST request, but the specified Content-Type was invalid. Valid types are: application/json application/x-www-form-urlencoded multipart/form-data text/plain.
member_analytics_disabledMember analytics are disabled for the team.
method_deprecatedThe method has been deprecated.
missing_argumentA required argument was not provided. The response's arg field names the missing argument. Arguments sent in a JSON body are ignored by methods that don't list application/json as a content type.
missing_post_typeThe method was called via a POST request and included a data payload, but the request did not include a Content-Type header.
missing_scopeThe token used is not granted the specific scope permissions required to complete this request.
no_permissionThe workspace token used in this request does not have the permissions necessary to complete the request. Make sure your app is a member of the conversation it's attempting to post a message to.
not_allowed_token_typeThe token type used in this request is not allowed.
not_an_adminThe token's user is not an owner or admin, and does not have permission to access the analytics API.
not_authedNo authentication token provided.
org_login_requiredThe workspace is undergoing an enterprise migration and will not be available until migration is complete.
rate_limitedThe organization has made too many calls to this method in a short amount of time. Wait and try again.
ratelimitedThe request has been ratelimited. Refer to the Retry-After header for when to retry the request.
request_timeoutThe method was called via a POST request, but the POST data was either missing or truncated.
service_unavailableThe service is temporarily unavailable
team_access_not_grantedThe token used is not granted the specific workspace access required to complete this request.
team_added_to_orgThe workspace associated with your request is currently undergoing migration to an Enterprise Organization. Web API and other platform operations will be intermittently unavailable until the transition is complete.
team_not_on_orgteam_id is not a workspace the token can access: it is not part of the token's organization, or the token is workspace-level and team_id is another workspace.
token_expiredAuthentication token has expired
token_revokedAuthentication token is for a deleted user or workspace or the app has been removed when using a user token.
two_factor_setup_requiredTwo factor setup is required.
