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

**URL:** <https://devforum.zoom.us/t/api-users-response-is-missing-fields-that-users-id-provides/95618>\
**Category:** API and Webhooks\
**Created:** [September 22, 2023, 2:41pm UTC](https://devforum.zoom.us/t/api-users-response-is-missing-fields-that-users-id-provides/95618 "2023-09-22T14:41:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jase\_Wells](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jase_wells/32/52321_2.png) [@Jase\_Wells](https://devforum.zoom.us/u/Jase_Wells)\
**Post date:** [September 22, 2023, 2:41pm UTC](https://devforum.zoom.us/t/api-users-response-is-missing-fields-that-users-id-provides/95618/1 "2023-09-22T14:41:45Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Jase\_Wells](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jase_wells/32/52321_2.png) [@Jase\_Wells](https://devforum.zoom.us/u/Jase_Wells)\
**Post date:** [September 22, 2023, 2:47pm UTC](https://devforum.zoom.us/t/api-users-response-is-missing-fields-that-users-id-provides/95618/2 "2023-09-22T14:47:31Z")

</div>

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

> [@Vanity name in /users listing](https://devforum.zoom.us/t/vanity-name-in-users-listing/1494):
>
> 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.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [September 26, 2023, 2:43pm UTC](https://devforum.zoom.us/t/api-users-response-is-missing-fields-that-users-id-provides/95618/3 "2023-09-26T14:43:15Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [October 2, 2023, 2:38pm UTC](https://devforum.zoom.us/t/api-users-response-is-missing-fields-that-users-id-provides/95618/4 "2023-10-02T14:38:24Z")

</div>

Closed on October 2, 2023, 2:38pm UTC

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.