Go to Slack


You're not signed into any teams. Sign in to test authentication.

Supported token types:
Expected scopes:

This method lets you find out information about a user's presence. Consult the presence documentation for more details.


This method has the URL https://slack.com/api/users.getPresence and follows the Slack Web API calling conventions.

Argument Example Required Description
token xxxx-xxxxxxxxx-xxxx Required

Authentication token bearing required scopes.

user W1234567890 Required

User to get presence info on. Defaults to the authed user.

Present arguments as parameters in application/x-www-form-urlencoded querystring or POST body. This method does not currently accept application/json.


When requesting information for a different user, this method just returns the current presence (either active or away).

    "ok": true,
    "presence": "active"

If you are requesting presence information for the authed user, this method returns the current presence, along with details on how it was calculated.

    "ok": true,
    "presence": "active",
    "online": true,
    "auto_away": false,
    "manual_away": false,
    "connection_count": 1,
    "last_activity": 1419027078

Typical error response

    "ok": false,
    "error": "invalid_auth"

presence indicates the user's overall presence, it will either be active or away.

online will be true if they have a client currently connected to Slack. auto_away will be true if our servers haven't detected any activity from the user in the last 30 minutes. manual_away will be true if the user has manually set their presence to away.

connection_count gives a count of total connections.

last_activity indicates the last activity seen by our servers. If a user has no connected clients then this property will be absent.


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 params in the response.

Error Description

No authentication token provided.


Invalid authentication token.


Authentication token is for a deleted user or workspace.


The workspace token used in this request does not have the permissions necessary to complete the request.


The 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.


The method was passed a PHP-style array argument (e.g. with a name like foo[7]). These are never valid with the Slack API.


The 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.


The 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.


The method was called via a POST request, but the specified Content-Type was invalid. Valid types are: application/x-www-form-urlencoded multipart/form-data text/plain.


The method was called via a POST request and included a data payload, but the request did not include a Content-Type header.


The 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.


The method was called via a POST request, but the POST data was either missing or truncated.


This table lists the expected warnings that this method will return. However, other warnings can be returned in the case where the service is experiencing unexpected trouble.

Warning Description

The method was called via a POST request, and recommended practice for the specified Content-Type is to include a charset parameter. However, no charset was present. Specifically, non-form-data content types (e.g. text/plain) are the ones for which charset is recommended.


The method was called via a POST request, and the specified Content-Type is not defined to understand the charset parameter. However, charset was in fact present. Specifically, form-data content types (e.g. multipart/form-data) are the ones for which charset is superfluous.

Argument Value
token Required Generate tokens to test with here.
user Required
Extra args