> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: About Business Schedules

## Article: About Business Schedules

## Article Link: https://dev.wix.com/docs/api-reference/business-management/calendar/about-business-schedules.md

## Article Content:

# About Business Schedules

Each business has a main schedule that defines its operating hours and availability.
The business schedule always uses the `externalId` value `4e0579a5-491e-4e70-a872-d097eed6e520`.

By default, each business has 5 recurring `WORKING_HOURS` events, 1 for each weekday (Monday through Friday) from 10 AM to 6 PM.
These `MASTER` events set the recurrence pattern that Wix Calendars uses to automatically calculate `INSTANCE` events.
Learn more about [recurring events](https://dev.wix.com/docs/api-reference/business-management/calendar/events-v3/recurring-events.md).

To identify the IDs of the 5 `MASTER` events, retrieve at least 1 of their corresponding `INSTANCE` events.
Call [Query Events](https://dev.wix.com/docs/rest/business-management/calendar/events-v3/query-events.md), specifying a date range that covers at least a full week and a query filter like this:

``` json
{
  "fromLocalDate": "2026-01-01T00:00:00",
  "toLocalDate": "2026-01-07T23:59:59",
  "query": {
    "filter": {
      "externalScheduleId": "4e0579a5-491e-4e70-a872-d097eed6e520",
      "type": "WORKING_HOURS"
    }
  }
}
```

For each weekday's `INSTANCE` working hour event that's returned, save its `id`, `recurringEventId`, and `scheduleId`.
The `recurringEventId` is the `id` of the corresponding `MASTER` event, which defines the recurrence pattern.
All 5 weekday `INSTANCE` events share a `scheduleId`, which is the business schedule's `id`.

To modify working hours:
- **Adjust existing hours**: Call [Update Event](https://dev.wix.com/docs/api-reference/business-management/calendar/events-v3/update-event.md) with the relevant master event ID to change the recurring pattern.
  For example, shift hours from 10 AM–6 PM to 9 AM–5 PM.
- **Add working hours**: Call [Create Event](https://dev.wix.com/docs/api-reference/business-management/calendar/events-v3/create-event.md) to add additional events of `"type": "WORKING_HOURS"`, `"recurrenceType": "MASTER"`, and the relevant `recurrenceRule`.
  Specify the business schedule `id` as the event's `scheduleId`.
  For example, add Saturday hours or an evening shift.
- **Remove a working day**: Call [Cancel Event](https://dev.wix.com/docs/api-reference/business-management/calendar/events-v3/cancel-event.md) with the master event ID to remove that day from the schedule.
- **Block holidays or time off**: Choose the appropriate method based on your blocking pattern:
  - **Single day**: Call [Cancel Event](https://dev.wix.com/docs/api-reference/business-management/calendar/events-v3/cancel-event.md) to remove the day's `INSTANCE` event, or [Update Event](https://dev.wix.com/docs/api-reference/business-management/calendar/events-v3/update-event.md) to shorten its hours.
  - **Longer period**: Call [Create Event](https://dev.wix.com/docs/api-reference/business-management/calendar/events-v3/create-event.md) with the business schedule ID as `scheduleId` and `start` and `end` dates spanning the entire period.
    For example, 2 weeks of summer vacation.
    Don't specify `recurrenceType`, the system creates a one-off blocking event by default.
  - **Recurring pattern**: Call [Create Event](https://dev.wix.com/docs/api-reference/business-management/calendar/events-v3/create-event.md) with the business schedule ID as `scheduleId`, `"recurrenceType": "MASTER"`, and the relevant `recurrenceRule`. The system creates a `DEFAULT` type event whose instances block availability.