Description
Recently we had the following problem: the /users/{userId} API endpoint returned a response without the email field. It is required for this type of request though. This happened two times (8/27 and 8/30) already.
Also, the first/last name had an empty value and created_at had a value, that is not related to the requested user.
Thank you for reaching out to Developer Support, happy to help here!
I am sorry to hear that this happened to you, this is an unexpected behavior of the API, you should be able to see the first and last name when you retrieve an user.
Have you experience this behavior any other times? is this happening still??
Thanks,
Elisa
Yea, we had the same problem several times yesterday, and we had to add a workaround to our code to stop failing on such responses (we just treat them like 404 responses). Maybe we had such a problem today, I just don’t know about that now.
If you want, I can add a new logging logic to collect such cases during the week. Would it be helpful?
Without being able to reproduce the issue, it’s difficult to say why this was happening. I’m not seeing any outages lining up with this. Please let us know if you log any further instances of this.
Thank you for following up here. It looks like that response has been modified from what the API returns. Would you be able to provide the full response? You can do that by sending an email to developersupport@zoom.us with a link to this thread and the response.
Actually, what I posted above is a full response body for the /users/imKtAjixQRW5KZ1TsipWhA API request. The status for the response is 200. What kind of additional info do you want me to provide? request/response headers? anything else?
What I mean is that typically the response would be formatted as JSON, with quotes, and there would be more properties that are returned. Here’s an example from our documentation:
Thank you for following up on this. Please send an email to developersupport@zoom.us with a link to this thread. In that email, please provide the App Name and App Owner Email. I’ll use that to reproduce the issue.
Just did that. I should clearly note that the issue might not be reproducible with the same UserId provided above, because after some time the issue is being resolved itself and API returns correct result with the full info about the user.