cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
76
Views
0
Helpful
2
Replies

Get Users by Location

connor-mcnamara
Community Member

I am trying to get all the users in a specified location. The /people endpoint has a parameter for locationId (https://developer.webex.com/calling/docs/api/v1/people/list-people), but it doesn't appear to work. When specifying a valid location ID, with the callingData flag set to true, I get the error - Calling Failure No user matching the locationId in this page. I can see on the Webex Admin Console that there are about a dozen users in this location. Attempting to specify one of those user's display names or email addresses in addition to the above parameters returns the same error. I can query those users without the locationId parameter set, but the information returned does not contain the user's location ID.

Attempting to query the API with the locationId set but with the callingData flag set to false or unspecified, returns a 403 error - calling flag not set. 

Am I doing something wrong or is there another API call I can use to get users by their location? 

1 Accepted Solution

wajidhassan
Level 4
Level 4

The locationId parameter in the /people API often does not work as expected, even when using callingData=true. This is a known limitation, and many users have reported that specifying a valid locationId still results in errors or no users being returned, despite those users being visible in Control Hub under the specified location.

The issue typically occurs when users do not have Webex Calling licenses properly assigned, or when the access token being used lacks the necessary admin privileges. Even though the API supports locationId in theory, in practice it’s inconsistent. As a workaround, you can retrieve all users with callingData=true and manually filter by locationId in your application logic, assuming the location data appears in the returned results.

If no location data is returned for users even with callingData=true, it could be due to missing entitlements or backend limitations in your organization. In that case, it’s best to open a Cisco TAC or Webex Developer Support case to confirm API behavior and entitlement configuration.

View solution in original post

2 Replies 2

wajidhassan
Level 4
Level 4

The locationId parameter in the /people API often does not work as expected, even when using callingData=true. This is a known limitation, and many users have reported that specifying a valid locationId still results in errors or no users being returned, despite those users being visible in Control Hub under the specified location.

The issue typically occurs when users do not have Webex Calling licenses properly assigned, or when the access token being used lacks the necessary admin privileges. Even though the API supports locationId in theory, in practice it’s inconsistent. As a workaround, you can retrieve all users with callingData=true and manually filter by locationId in your application logic, assuming the location data appears in the returned results.

If no location data is returned for users even with callingData=true, it could be due to missing entitlements or backend limitations in your organization. In that case, it’s best to open a Cisco TAC or Webex Developer Support case to confirm API behavior and entitlement configuration.

Thanks, that is helpful! Our order is still in process so we don't have Webex calling licenses applied yet, which I suspect might be the issue based on your post. Appreciate the insight.