Format Your New Topic as Follows:
API Endpoint(s) and/or Zoom API Event(s)
Link the API endpoint(s) and/orZoom API Event(s) you’re working with to help give context.
List common areas does not allow for providing a keyword so every single common area needs to be fetched and checked to see if an extension matched.
List phone users allows you to provide a keyword so if we know it’s a user it’s relatively straight forward to find the user.
Description
We assign a single extension to every user or common area. That extension is used to manage a phone service item in our system, as we bill account using the extensions they have.
There is no way to find what is associated to an extension in Zoom by extension number without having the extension id which we do not want to store in our databases. We can’t find a phone service by extension without making several unnecessary requests, i.e. iterating over every common area to find one that matches. We are heavy users of the Zoom API for provisioning and management so we don’t want to have iterative requests to find this kind of data.
What are the limitations of adding an endpoint to get an extension by extensionNumber? Or providing a filter on common area items to search by keyword like with the phone users.