# SCIM Get User error 400

**URL:** <https://devforum.zoom.us/t/scim-get-user-error-400/13900>\
**Category:** API and Webhooks\
**Created:** [April 19, 2020, 3:02pm UTC](https://devforum.zoom.us/t/scim-get-user-error-400/13900 "2020-04-19T15:02:51Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![TcChung](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tcchung/32/1112_2.png) [@TcChung](https://devforum.zoom.us/u/TcChung)\
**Post date:** [April 19, 2020, 3:02pm UTC](https://devforum.zoom.us/t/scim-get-user-error-400/13900/1 "2020-04-19T15:02:51Z")

</div>

**Description**  
Zoom SCIM API returns error 400 when Azure sends an initial request.

**Error**  
Normally Zoom returns a message with status 200 after Azure send a test request before account provisioning. Starting from today, zoom returns status 400, making azure stops provisioning.

**Which App Type (OAuth / Chatbot / JWT / Webhook)?**  
JWT SCIM user API

**Which Endpoint/s?**  
scim/Users

Call log before:  
{  
endpoint: “[https://api.zoom.us/scim/Users](https://api.zoom.us/scim/Users)”,  
response\_headers: [  
“Set-Cookie: zm\_aid=”"; [Domain=.zoom.us](http://Domain=.zoom.us); Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly"  
],  
date\_time: “2020-04-19 15:42:13”,  
method: “GET”,  
request\_body: “N/A”,  
response: {  
schemas: [  
“urn:ietf:params:scim:api:messages:2.0:ListResponse”  
],  
totalResults: 0,  
startIndex: 1,  
itemsPerPage: 0,  
Resources: [  
]  
},  
request\_headers: [  
“authorization: \*\*\*\*\*\*”,  
“connection: close”  
],  
request\_params: [  
“filter: userName eq “AzureAD\_Test-abf00683-c088-474a-a15e-07c35f3eb29d””  
],  
http\_status: “200”  
}

Call log after:  
{  
endpoint: “[https://api.zoom.us/scim/Users](https://api.zoom.us/scim/Users)”,  
response\_headers: [  
“Set-Cookie: zm\_aid=”"; [Domain=.zoom.us](http://Domain=.zoom.us); Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly"  
],  
date\_time: “2020-04-19 15:49:29”,  
method: “GET”,  
request\_body: “N/A”,  
response: {  
schemas: [  
“urn:ietf:params:scim:api:messages:2.0:Error”  
],  
detail: “User AzureAD\_Test-36bf9236-1ff7-432d-8375-6830f741cb61 not exist or not belong to this account.”,  
status: 400  
},  
request\_headers: [  
“authorization: \*\*\*\*\*\*”,  
“connection: close”  
],  
request\_params: [  
"filter: userName eq “AzureAD\_Test-36bf9236-1ff7-432d-8375-6830f741cb61"”  
],  
http\_status: “400”  
}

---

<div class="post-metadata">

**Author:** ![hsheppard](https://avatars.discourse-cdn.com/v4/letter/h/d07c76/32.png) [@hsheppard](https://devforum.zoom.us/u/hsheppard)\
**Post date:** [April 19, 2020, 11:23pm UTC](https://devforum.zoom.us/t/scim-get-user-error-400/13900/2 "2020-04-19T23:23:54Z")

</div>

I’m getting the same error. Please investigate Zoom.

---

<div class="post-metadata">

**Author:** ![it-procurement](https://avatars.discourse-cdn.com/v4/letter/i/fbc32d/32.png) [@it-procurement](https://devforum.zoom.us/u/it-procurement)\
**Post date:** [April 20, 2020, 9:24am UTC](https://devforum.zoom.us/t/scim-get-user-error-400/13900/3 "2020-04-20T09:24:02Z")

</div>

Hi, this error started for us as well for first time on Apr 19 at 07:47 AM UTC, and Azure provisioning is now quarantined

---

<div class="post-metadata">

**Author:** ![michael.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael.zoom/32/37213_2.png) [@michael.zoom](https://devforum.zoom.us/u/michael.zoom)\
**Post date:** [April 21, 2020, 4:01am UTC](https://devforum.zoom.us/t/scim-get-user-error-400/13900/4 "2020-04-21T04:01:05Z")

</div>

Hi @TcChung @hsheppard & @it-procurement, we’re investigating this, I’ll get back when we have an updated.

---

<div class="post-metadata">

**Author:** ![it-procurement](https://avatars.discourse-cdn.com/v4/letter/i/fbc32d/32.png) [@it-procurement](https://devforum.zoom.us/u/it-procurement)\
**Post date:** [April 21, 2020, 8:30am UTC](https://devforum.zoom.us/t/scim-get-user-error-400/13900/5 "2020-04-21T08:30:44Z")

</div>

Seems to be working again for us. I assume this is related to throttling being introduced on the API on 19th April.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [April 22, 2020, 12:03am UTC](https://devforum.zoom.us/t/scim-get-user-error-400/13900/6 "2020-04-22T00:03:29Z")

</div>

Happy to hear it is working @it-procurement! 🙂

Please let us know if you experience additional issues.

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 8:52pm UTC](https://devforum.zoom.us/t/scim-get-user-error-400/13900/7 "2020-08-21T20:52:23Z")

</div>