Genesys Cloud - Developer Community!

The /telephony/providers/edges/phones API call Genesys Cloud Developer Center takes some "expand" selections. Unfortunately, I could not find one that will cause the response to include the webRTCUser details, that are present via the /telephony/providers/edges/phones/{phoneId} API call.

One of the chronic issues we've had is that as users are deactivated via Microsoft Entra ID for Genesys Cloud SCIM, the phone remains. We'd like the opportunity to cross-reference phone assignment against the activation state of the user and mass de-provision for conciseness.

Genesys		remove preview
Genesys Cloud Developer Center Developer-focused guides, tutorials, API Documentation, videos, and more for Genesys Cloud View this on Genesys >

 

#PlatformAPI

------------------------------
Shaddy Baddah
Genesys Voice Engineer
------------------------------

Hello,

You can request support for new use cases or features submitting a Genesys Cloud idea and let other vote for it.

Regards,

------------------------------
Jerome Saint-Marc
Senior Development Support Engineer
------------------------------

Hi Shaddy,

I looked into this while working on phone inventory automation and, as far as I can tell, the collection endpoint:

GET /api/v2/telephony/providers/edges/phones

does not expose the same level of detail as:

GET /api/v2/telephony/providers/edges/phones/{phoneId}

and I have not found any documented expand option that returns the WebRTC user assignment details in the collection response.

For that reason, the approach I would recommend is:

1. Retrieve the phone inventory using the collection endpoint.
2. For phones that require validation, query the individual phone endpoint to retrieve the detailed configuration and user association information.
3. Cross-reference those users against your SCIM-managed user population.
4. Remove or unassign orphaned WebRTC phones as part of a periodic cleanup process.

For the deprovisioning use case specifically, I would actually consider the user lifecycle to be the source of truth rather than the phone inventory itself. Since SCIM user deactivation and phone lifecycle management are separate processes, a scheduled reconciliation job is often more reliable than trying to infer account status directly from phone assignments.

------------------------------
Gabriel Garcia
NA
------------------------------