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”
}’