Description

We are deprecating the ability to change another user’s presence through the PATCH API without a permission. After this change customers will be required to have the presence:userPresence:edit permission to update another user’s presence. See Deprecation: Permission enforcement change to update another user's presence with the PATCH API.

Change Category

API

Change Context

We understand that the current unrestricted ability to modify another user's presence via the PATCH API can be viewed as a potential security risk. To address this, we are introducing a specific permission to control this capability.

Change Impact

Effective July 20, 2025, updating another user's presence using the presence PATCH API will require the user making the change to have the presence:userPresence:edit permission.

Currently, it is possible to update another user's presence through the PATCH API using an undocumented method. This upcoming permission enforcement will resolve this. Starting April 21, 2025, users can add the presence:userPresence:edit permission so that they can update another user’s presence even after July 20, 2025.

Date of Change

20 Jul 2025

Impacted APIs

Am I affected?
If you or anyone in your organization uses the following endpoints to update other user’s presence, you will be impacted:

PATCH /api/v2/users/{userId}/presences/purecloud
PATCH /api/v2/users/{userId}/presences/{sourceId}

References

[PURE-4184]