---
title: "Create a sub-schedule"
method: POST
path: "/schedules/{subdomain}/groups"
tags: ["Sub-schedules"]
---

# Create a sub-schedule

`POST /schedules/{subdomain}/groups`

Creates a new sub-schedule within a schedule. Requires a Pro plan. The slug is automatically generated from the name.

## Path parameters

- `subdomain` string, required

## Request body

- object
  - `name` string, required — Name of the sub-schedule
  - `color` string — Color for the sub-schedule (e.g. hex code)

## Response `201`

Sub-schedule created successfully

- object
  - `data` Group
    - `id` string — Encoded sub-schedule ID
    - `name` string — Sub-schedule name
    - `slug` string — URL-friendly slug
    - `color` string, nullable — Color associated with this sub-schedule

## Other responses

- `401` — Missing or invalid API key
- `403` — Not a Pro account
- `404` — Schedule not found
- `422` — Validation error

## Changes

- **2026-02-11** `e24c8532211b` — 1 info
  - api operation id `create_group` was added
- **2026-02-11** `36ccba39bc4d` — 1 info
  - api operation id `create_group` removed and replaced with ``

[Change history](https://skmtc.dev/eventschedule/apis/event-schedule-api/changes/schedules/:subdomain/groups/post.md)

---

[API](https://skmtc.dev/eventschedule/apis/event-schedule-api.md) · [All operations](https://skmtc.dev/eventschedule/apis/event-schedule-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/eventschedule/event-schedule-api/revisions/fc24d7d227c4/schema)