---
title: "Deletes a schedule group."
method: DELETE
path: "/api/v1/schedule-groups/{id}"
tags: ["ScheduleGroups"]
---

# Deletes a schedule group.

`DELETE /api/v1/schedule-groups/{id}`

## Request

- Base URL: `https://app.flexonthejob.com`
- URL: `https://app.flexonthejob.com/api/v1/schedule-groups/{id}`
- Auth: HTTP bearer

Requires `ManageJobs` and an `Idempotency-Key` header. The same soft delete as the
Schedule Groups page: the group and its memberships disappear, and jobs assigned under it keep
their assignees (only the group context on those assignments is cleared). Refused with
`409` while the group still has child groups — delete or move those first.

## Path parameters

- `id` integer, required

## Response `200`

The group was deleted; body carries its id and a confirmation message.

- ApiOperationResponse: Body of a successful workflow-style write that has no richer resource to return (assign, start, complete, void…). Id is the affected resource's id; Warning carries a non-fatal note from the service (e.g. an email that could not be sent).
  - `id` integer: Id of the resource the operation acted on (e.g. the job id).
  - `message` string, nullable: Human-readable confirmation from the service (e.g. "Job started."). May be null.
  - `warning` string, nullable: Non-fatal problem encountered while completing the operation (e.g. a notification email that could not be sent). Null when there was none.

## Other responses

- `400`: Missing `Idempotency-Key`.
- `401`: Unauthorized
- `403`: The `scheduling` module is not active for this organization.
- `404`: No such group in this organization (also for already-deleted groups).
- `409`: The group still has child groups, or the key's creator is unknown on this server.
- `429`: Too Many Requests

---

[API](https://skmtc.dev/flexonthejob/apis/flex-api.md) · [All operations](https://skmtc.dev/flexonthejob/apis/flex-api/llms.txt) · [OpenAPI document](https://skmtc.dev/flexonthejob/apis/flex-api/revisions/19c8f4d27acf?raw)