API Endpoint(s) and/or Zoom API Event(s)
GET /scheduler/users/{userId}
Description
Some users are returning 403 Forbidden on the scheduler/users/ endpoint despite being part of the same organization. Fetching all other users work as intended, just four users so far we have identified that show this error on this endpoint, and all scheduler/ endpoints that require a userId.
Error?
{
"error": {
"code": 403,
"errors": [
{
"appCode": 0,
"domain": "global",
"message": "invalid user",
"reason": "forbidden"
}
],
"message": "invalid user",
"reqId": "ZMAIL_7c0361f13f38942da8a720c466cf1e19",
"status": "FORBIDDEN"
}
}
How To Reproduce
Steps to reproduce the behavior:
**Fetch user scheduler information from the GET scheduler/user/{userId} endpoint
curl --location 'https://api.zoom.us/v2/scheduler/users/{userId}' \
--header 'Authorization: Bearer {bearer_token}' \
Authentication method or app type
Request done with a bearer token with grant_type: account_credentials with Admin permissions on a Server-to-Server applications.
Resulting payload
{
"error": {
"code": 403,
"errors": [
{
"appCode": 0,
"domain": "global",
"message": "invalid user",
"reason": "forbidden"
}
],
"message": "invalid user",
"reqId": "ZMAIL_7c0361f13f38942da8a720c466cf1e19",
"status": "FORBIDDEN"
}
}
Additional Information
Credentials are working since with the same credentials I can fetch other users of the same organization and it returns the information correctly, it is just four users so far that we have identified. If you need the specific information DM me and I can provide which which users exactly it happens and give you the full CURL request without expunged data.
