# Zoom Scheduler API — How do I represent a single fully closed date against recurring availability?

**URL:** <https://devforum.zoom.us/t/zoom-scheduler-api-how-do-i-represent-a-single-fully-closed-date-against-recurring-availability/147317>\
**Category:** API and Webhooks\
**Created:** [October 21, 2026, 5:41am UTC](https://devforum.zoom.us/t/zoom-scheduler-api-how-do-i-represent-a-single-fully-closed-date-against-recurring-availability/147317 "2026-10-21T05:41:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ASS.LLC](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ass.llc/32/77431_2.png) [@ASS.LLC](https://devforum.zoom.us/u/ASS.LLC)\
**Post date:** [October 21, 2026, 5:41am UTC](https://devforum.zoom.us/t/zoom-scheduler-api-how-do-i-represent-a-single-fully-closed-date-against-recurring-availability/147317/1 "2026-10-21T05:41:01Z")

</div>

PATCH /v2/scheduler/availability/{availabilityId}

Documentation:

> **[Scheduler API - Scheduler - Zoom Developer Docs](https://developers.zoom.us/docs/api/scheduler/#tag/availability/patch/scheduler/availability/%7BavailabilityId%7D)**
>
> The Zoom Developer Platform is an open platform that allows third-party developers to build applications and integrations upon Zoom’s video-first unified communications platform.

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

1. Request URL / Headers / Body

PATCH [https://api.zoom.us/v2/scheduler/availability/{availabilityId}](https://api.zoom.us/v2/scheduler/availability/%7BavailabilityId%7D)

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.

1. Authentication method / app type

Account-level Server-to-Server OAuth

Relevant scope:

scheduler:update:availability:admin

1. 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:

> [@Updating Scheduler PATCH/scheduler/schedules/{scheduleId} returns 400 when updating availability rule containing time for Wednesday](https://devforum.zoom.us/t/updating-scheduler-patch-scheduler-schedules-scheduleid-returns-400-when-updating-availability-rule-containing-time-for-wednesday/122238):
>
> API Endpoint(s) and/or Zoom API Event(s) Patch schedules​ PATCH /scheduler/schedules/{scheduleId} Description When updating a scheduler through the API, we were experiencing unusual 400 responses and we were not able to identify where for days. Accidentally we figured out that it was on the availability\_rules section of the payload. Specifically segments\_recurrence. When sending a recurrence for any day other than Wednesday, it works correctly. But when sending for Wednesday (being only Wedn…

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?
