# Scheduling Status Updates

**URL:** <https://devforum.zoom.us/t/scheduling-status-updates/140021>\
**Category:** API and Webhooks\
**Created:** [December 17, 2025, 9:10pm UTC](https://devforum.zoom.us/t/scheduling-status-updates/140021 "2025-12-17T21:10:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![LowlyDev](https://avatars.discourse-cdn.com/v4/letter/l/7ab992/32.png) [@LowlyDev](https://devforum.zoom.us/u/LowlyDev)\
**Post date:** [December 17, 2025, 9:10pm UTC](https://devforum.zoom.us/t/scheduling-status-updates/140021/1 "2025-12-17T21:10:11Z")

</div>

* * *

**API Endpoint(s) and/or Zoom API Event(s)**  
Endpoint: /v2/contact\_center/users/{user\_id}/status

**Description**

I have been looking for a way to ‘schedule’ away reasons - e.g. user is on leave next week and we want their status to show as on leave without them manually doing it, users may tend to forget this….

_The documentation indicates that the PATCH request should contain status\_id and sub\_status\_id. This works changing it real time. I found an additional article (on either reddit or stackoverflow , sorry - cant remember which) that stated it could also accept_ scheduled\_start and scheduled\_end. I added these fields, the API returned an response:,“http\_code”:204,“success”:true} message, but it did not save as when queried, it showed empty.

I am curious, why would the API not return an error if the field was unsupported? I am assuming at this point it is not supported (or I have the wrong field name etc), but if anyone knows the right format, endpoiont, or another solution or workaround, it would be appreciated.

**Error?**  
_No error message supplied._

**How To Reproduce**  
_Steps to reproduce the behavior:_  
_1._ curl -X PATCH “{baseurl}/v2/contact\_center/users/{userid}/status” \  
-H “Authorization: Bearer ${TOKEN}” \  
-H “Content-Type: application/json” \  
-d ‘{  
“status\_id”: “2”,  
“sub\_status\_id”: “{substatusid}”,  
“scheduled\_start”: “20-12-2025”,  
“scheduled\_end”: “20-12-2025”  
}’

---

<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:** [December 23, 2025, 9:12pm UTC](https://devforum.zoom.us/t/scheduling-status-updates/140021/2 "2025-12-23T21:12:41Z")

</div>

Hi @LowlyDev  
Can you try not passing the scheduled\_start and scheduled\_end fields in your request, those values are not documented, so I am wondering if this could be affecting the API call

Looping @rehema.zoom for more input