---
title: "Create a schedule"
method: POST
path: "/v2/schedules"
tags: ["Schedules"]
---

# Create a schedule

`POST /v2/schedules`

Create a schedule for the authenticated user.

      The point of creating schedules is for event types to be available at specific times.

      The first goal of schedules is to have a default schedule. If you are platform customer and created managed users, then it is important to note that each managed user should have a default schedule.
      1. If you passed `timeZone` when creating managed user, then the default schedule from Monday to Friday from 9AM to 5PM will be created with that timezone. The managed user can then change the default schedule via the `AvailabilitySettings` atom.
      2. If you did not, then we assume you want the user to have this specific schedule right away. You should create a default schedule by specifying
      `"isDefault": true` in the request body. Until the user has a default schedule the user can't be booked nor manage their schedule via the AvailabilitySettings atom.

      The second goal of schedules is to create another schedule that event types can point to. This is useful for when an event is booked because availability is not checked against the default schedule but instead against that specific schedule.
      After creating a non-default schedule, you can update an event type to point to that schedule via the PATCH `event-types/{eventTypeId}` endpoint.

      When specifying start time and end time for each day use the 24 hour format e.g. 08:00, 15:00 etc.

      <Note>Please make sure to pass in the cal-api-version header value as mentioned in the Headers section. Not passing the correct value will default to an older version of this endpoint.</Note>

## Headers

- `Authorization` string, required
- `cal-api-version` string, required

## Request body

- CreateScheduleInput20240611
  - `name` string, required
  - `timeZone` string, required — Timezone is used to calculate available times when an event using the schedule is booked.
  - `availability` ScheduleAvailabilityInput20240611[] — Each object contains days and times when the user is available. If not passed, the default availability is Monday to Friday from 09:00 to 17:00.
    - `days` string[], required — Array of days when schedule is active.
    - `startTime` string, required — startTime must be a valid time in format HH:MM e.g. 08:00
    - `endTime` string, required — endTime must be a valid time in format HH:MM e.g. 15:00
  - `isDefault` boolean, required — Each user should have 1 default schedule. If you specified `timeZone` when creating managed user, then the default schedule will be created with that timezone. Default schedule means that if an event type is not tied to a specific schedule then the default schedule is used.
  - `overrides` ScheduleOverrideInput20240611[] — Need to change availability for a specific date? Add an override.
    - `date` string, required
    - `startTime` string, required — startTime must be a valid time in format HH:MM e.g. 12:00
    - `endTime` string, required — endTime must be a valid time in format HH:MM e.g. 13:00

## Response `201`

- CreateScheduleOutput20240611
  - `status` 'success' | 'error', required
  - `data` ScheduleOutput20240611, required
    - `id` number, required
    - `ownerId` number, required
    - `name` string, required
    - `timeZone` string, required
    - `availability` ScheduleAvailabilityInput20240611[], required
      - `days` string[], required — Array of days when schedule is active.
      - `startTime` string, required — startTime must be a valid time in format HH:MM e.g. 08:00
      - `endTime` string, required — endTime must be a valid time in format HH:MM e.g. 15:00
    - `isDefault` boolean, required
    - `overrides` ScheduleOverrideInput20240611[], required
      - `date` string, required
      - `startTime` string, required — startTime must be a valid time in format HH:MM e.g. 12:00
      - `endTime` string, required — endTime must be a valid time in format HH:MM e.g. 13:00

---

[API](https://skmtc.net/calcom/apis/cal-diy-api-v2.md) · [All operations](https://skmtc.net/calcom/apis/cal-diy-api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/calcom/cal-diy-api-v2/revisions/16de9d3eb7b3/schema)