Get User Presence

Returns the online status of the specified user.
Get presence information about a particular user.
User ID as a decimal integer
If true, a local query will be performed and the presence will be set to OFFLINE for users who are not local to the calling user's pod. If false or absent, then the presence of all local users and the presence of all external users to whom the calling user is connected will be queried. For external users, a "presence interest" should be registered through /v1/user/presence/register before querying for presence.
Session authentication token.
200: OK
400: Bad Request
Client error, see response body for further details.
401: Unauthorized
Unauthorized: Invalid session token.
403: Forbidden
Forbidden: Caller lacks necessary entitlement.
404: Not Found
Not Found: user id cannot be located.
500: Internal Server Error
Server error, see response body for further details.
The timestamp in the response is in UTC format and contains the time when the presence was set using Set Presence. For users who are offline, the timestamp contains the current time when the Get User Presence endpoint was invoked.
To get the presence of external users, you must first register interest about their presence.
When calling this as an OBO-enabled endpoint, use the OBO User Authenticate token for sessionToken.
The available online status values (presence categories) for users are listed on the Get Presence page.

Query Presence of External Users

To query the presence of external users, you must first perform an additional step:
  1. 1.
    Call the Register Interest in External User Presence endpoint to register interest in those users.
  2. 2.
    Call this endpoint to query the presence of each user.
To query the presence of internal users, you do not need to register interest and can call this endpoint directly.
Last modified 2mo ago