mk_telephony | 2018-10-30 01:58:33 UTC | #1
What is the expected behaviour if the sourceID for the get/patch presence endpoints is set to a string that is not PURECLOUD? We are also setting isPrimary to true when making the patch request.
get: https://developer.mypurecloud.com/api/rest/v2/presence/index.html#getUserPresence patch: https://developer.mypurecloud.com/api/rest/v2/presence/index.html#patchUserPresence
We tried patching/getting a purecloud user's presence by sending a different sourceID (e.g. "test") via the API. However this results in any state changes via the purecloud UI to no longer reflect the true state of the user (even though the UI may reflect it), resulting in a potential out-of-sync state scenario.
What is the intended behaviour here? Can we send a custom sourceId as we are currently doing? In that case does the user have multiple concurrent states, one for each source?
tim.smith | 2018-10-30 13:09:47 UTC | #2
The source ID must always be PURECLOUD in all situations.
system | 2018-11-30 13:10:48 UTC | #3
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 3847