PATCH /v2/scheduler/availability/{availabilityId}
Documentation:
Description
I maintain a shared Zoom Scheduler availability object that is used by two schedules:
- one 30-minute schedule
- one 60-minute schedule
Both schedules reference the same availability object. Zoom correctly derives different available_times for each schedule based on its duration.
My recurring availability is:
- Monday: 09:00–16:00
- Wednesday: 09:00–16:00
- Thursday: 09:00–16:00
- Friday: 09:00–16:00
I also maintain date-specific availability overrides using the top-level segments array.
The problem is how to represent a normally recurring date as completely unavailable.
Example:
Thursday 2026-11-26 normally inherits:
09:00–16:00
from segments_recurrence, but that specific date needs to have ZERO availability.
Historically, our integration represented a closed date using a zero-duration date-specific segment:
{
“start”: “2026-11-26T16:00:00.000Z”,
“end”: “2026-11-26T16:00:00.000Z”
}
Zoom Technical Support traced our request through the Scheduler backend and confirmed that the service currently requires every segment’s end time to be strictly later than its start time.
They also confirmed that the other non-zero-duration intervals in the submitted payload passed validation.
Simply omitting 2026-11-26 from the date-specific segments array does not appear safe for this use case because the normal Thursday recurrence can apply again, which would expose public booking times on a date that should be closed.
The current API documentation describes segments as:
“The date on which the rule needs to be applied outside of the availability rule”
and the segment itself as:
“The date interval that needs to [be] overridden.”
However, the documentation only provides examples containing positive-duration intervals.
I cannot find a documented representation for a date-specific override whose resulting availability should be empty.
My question is:
What is the supported Zoom Scheduler API representation for:
“Thursday is normally available 09:00–16:00 every week, but Thursday 2026-11-26 should have zero availability”?
Specifically, is there a supported:
- date-specific exclusion
- closed-date exception
- empty date override
- availability exception object
- or another API representation
for suppressing recurrence on one specific date?
I do not want to use an undocumented workaround such as a 1-minute availability interval unless Zoom confirms that this is the intended or supported approach.
Error
HTTP 400
{
“error”: {
“code”: 400,
“errors”: [
{
“appCode”: 0,
“domain”: “global”,
“message”: “end time no later than start time.”,
“reason”: “invalidArgument”
}
],
“message”: “end time no later than start time.”,
“reqId”: “WEB_da9a2d9a2a8d2ac785ebf816a75fc783”,
“status”: “INVALID_ARGUMENT”
}
}
Zoom Technical Support confirmed that this validation error is specifically caused by zero-duration segments where:
start == end
How To Reproduce
- Request URL / Headers / Body
PATCH https://api.zoom.us/v2/scheduler/availability/{availabilityId}
Headers:
Content-Type: application/json
Authorization: Bearer
Sanitized example body:
{
“name”: “My Availability”,
“time_zone”: “America/Denver”,
“default”: true,
“segments”: [
{
“start”: “2026-11-26T16:00:00.000Z”,
“end”: “2026-11-26T16:00:00.000Z”
}
],
“segments_recurrence”: {
“mon”: [
{
“start”: “09:00”,
“end”: “16:00”
}
],
“wed”: [
{
“start”: “09:00”,
“end”: “16:00”
}
],
“thu”: [
{
“start”: “09:00”,
“end”: “16:00”
}
],
“fri”: [
{
“start”: “09:00”,
“end”: “16:00”
}
]
}
}
The date 2026-11-26 is a Thursday and normally inherits the Thursday recurrence, but should be completely unavailable.
- Authentication method / app type
Account-level Server-to-Server OAuth
Relevant scope:
scheduler:update:availability:admin
- Error
HTTP 400
INVALID_ARGUMENT
end time no later than start time.
Request ID:
WEB_da9a2d9a2a8d2ac785ebf816a75fc783
Additional Context
Zoom Technical Support confirmed the following after tracing the request:
- the request is reaching the Scheduler service
- zero-duration segments are rejected by validation
- every segment’s end time must be strictly later than its start time
- the remaining positive-duration intervals in the same payload passed validation
They were unable to confirm why the zero-duration convention appeared to work in our August 2026 testing because their logs only retain 15 days.
I also found this prior Zoom Developer Forum thread involving:
PATCH /scheduler/schedules/{scheduleId}
where otherwise valid availability_rules / segments_recurrence payloads returned HTTP 400 because of a Zoom-side validation bug:
Zoom reproduced that issue internally and later fixed it.
That appears separate from my primary question here, which is specifically the supported representation for a date-specific full closure when using:
PATCH /scheduler/availability/{availabilityId}
The exact answer I am looking for is:
What JSON should be sent to represent:
Thursday recurring availability:
09:00–16:00
but for:
2026-11-26
availability should be:
none
while all other Thursdays continue using the normal recurrence?