# Zoom API Invalid Access Token Behavior Change

**URL:** <https://devforum.zoom.us/t/zoom-api-invalid-access-token-behavior-change/114327>\
**Category:** Authentication\
**Tags:** api, contact\_center\
**Created:** [July 25, 2024, 12:03am UTC](https://devforum.zoom.us/t/zoom-api-invalid-access-token-behavior-change/114327 "2024-07-25T00:03:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![reese](https://avatars.discourse-cdn.com/v4/letter/r/91b2a8/32.png) [@reese](https://devforum.zoom.us/u/reese)\
**Post date:** [July 25, 2024, 12:03am UTC](https://devforum.zoom.us/t/zoom-api-invalid-access-token-behavior-change/114327/1 "2024-07-25T00:03:02Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**

- /v2/contact\_center/users

**Description**  
Starting July 19, 2024, we have noticed a change in the way this endpoint responds when an invalid token (i.e. expired) is used. Our Zoom Contact Center API client is written to expect an HTTP status code of **400** and a response body like:

```auto
{"code": 124}

```

However, since July 19th, when an invalid token (i.e. expired) is used, this endpoint responds with an HTTP status code of **401** and a response body of:

```auto
{"status": false, "errorCode": 401}

```

This change in behavior is really 3 different changes:

1. Different HTTP status code (401 instead of 400)
2. Different response body error code (401 instead of 124)
3. Different attribute inside the response body (errorCode instead of code)

I searched this forum, I checked the Zoom developers docs, API references, and changelogs, but I could not find any mention anywhere of these changes. Considering Zoom has been providing warnings about certain Contact Center endpoints being deprecated (developers(dot)zoom(dot)us/docs/api/rest/contact-center-api/endpoint-deprecation-faq) for months and months, I would like to believe they would have also provided sufficient warning about this change.

My questions are:

1. Is this change in behavior, described above, expected?
2. If so, why was this change not communicated in advance?
3. If this change is unexpected, is it being changed back, or should we update our Zoom API client to handle this new behavior?

---

<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:** [August 1, 2024, 2:01pm UTC](https://devforum.zoom.us/t/zoom-api-invalid-access-token-behavior-change/114327/2 "2024-08-01T14:01:37Z")

</div>

Hi @reese  
Thanks for reaching out to us and for bringing this to our attention.  
Allow me to do some internal research on this issue and will get back to your with my findings.  
Cheers,  
Elisa

---

<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:** [August 6, 2024, 7:38pm UTC](https://devforum.zoom.us/t/zoom-api-invalid-access-token-behavior-change/114327/3 "2024-08-06T19:38:53Z")

</div>

To update this thread, I am currently looking into this!

---

<div class="post-metadata">

**Author:** ![bautrey-glia](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bautrey-glia/32/74465_2.png) [@bautrey-glia](https://devforum.zoom.us/u/bautrey-glia)\
**Post date:** [July 2, 2026, 10:57am UTC](https://devforum.zoom.us/t/zoom-api-invalid-access-token-behavior-change/114327/4 "2026-07-02T10:57:33Z")

</div>

I still want an update on this thread. I could not find any documentation for this change in API behaviour.

Zoom frequently breaks our API contracts with our integration and its becoming a nuisance.