API /users response is missing fields that /users/ID provides

[Jase_Wells]

I’m using the API to integrate Zoom details into our users’ corporate intranet profiles — for example, so their meeting URL can be shown internally.

So I call /users to get all our active users in Zoom and loop through them to see who has a vanity_url and personal_meeting_url set. Except those fields aren’t included in the user object from the /users response! So for every user, I have to make another call to /users/ID to fetch their details, which does include their vanity URL and personal meeting URL.

Obviously this is pretty inefficient. If we have 300 users, I have to make 301 API calls instead of just one. Am I missing something? Is there another way to get all our users’s vanity/meeting URLs?

[Jase_Wells]

Oops, I guess I already asked about this 5 years ago:

Vanity name in /users listing

Any chance you might add the vanity_name field into the GET /users response? We use the API to periodically fetch our users and update their Zoom details on our intranet directory. Their PMI gets included in the results, but since vanity_name does not, we have to fetch every user one-by-one to get that info. If it was included in the /users response, that would eliminate a lot of extra requests.

[elisa.zoom (Elisa)]

Hi @Jase_Wells
Thanks for reaching out to us again
You are right, in our GET/users endpoint you can not get the vanity_url but you can get the PMI value.
Other than that yes you will have to fetch the GET/users/id to get user details.
I understand this is inefficient for you cause you have a lot of users but unfortunately I do not belive ther is another way to get vanity URL