> For the complete documentation index, see [llms.txt](https://docs.stellic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stellic.com/stellic-partner-api/catalog-sections/delete-a-catalog-section.md).

# Delete a catalog section

Use this endpoint to remove a cancelled section right away instead of waiting for your next data sync, so students stop planning around it. The section is removed the same way your data sync removes a section that drops out of the feed. Only sections in the current term or a later one can be deleted.

## DELETE /catalog/section/{id}

>

```json
{"openapi":"3.0.0","info":{"title":"Stellic for Developers","version":"1.0"},"tags":[{"name":"Catalog Sections"}],"servers":[{"url":"https://{institution}.stellic.com/partnerapi/v1","variables":{"institution":{"default":"{institution}","description":"Your institution's Stellic subdomain: the part before `.stellic.com` in the URL you use to sign in. It becomes the host in every request, as in `https://{institution}.stellic.com/partnerapi/v1/...`. Replace the `{institution}` placeholder with your subdomain before sending."}}}],"security":[{"bearerAuth":[]}],"components":{"securitySchemes":{"bearerAuth":{"type":"http","scheme":"bearer","description":"Personal Access Token issued by your Stellic integration partner. Send it as `Authorization: Bearer <token>` on every request. One token per institution; do not share across environments."}}},"paths":{"/catalog/section/{id}":{"delete":{"tags":["Catalog Sections"],"parameters":[{"name":"id","in":"path","required":true,"description":"Catalog ID of the section (the section ID your data sync carries). Leading and trailing spaces are trimmed.","schema":{"type":"string"}}],"responses":{"200":{"description":"Section deleted permanently, along with its meeting times, section details, instructors, tags, restrictions, students' permission to register for it, and students' section enrollments in it. Other sections that named it as an auto-enroll section are left with none. The section's cached data and seat counts are cleared right away.","content":{"application/json":{"schema":{"type":"object","properties":{"success":{"type":"boolean"}}}}}},"400":{"description":"The section can't be deleted. Nothing is deleted.\n\nThe response is an `application/json` object with an `errors` array of `{\"message\": \"...\"}` objects.\n\nCommon causes:\n- The section is in a term before the current one - returns `Course section with id:{id} is in past term:{term} and cannot be deleted`\n- More than one section carries `{id}` - returns `Course section id {id} matches more than one section`"},"401":{"description":"Missing or invalid Bearer token."},"403":{"description":"Your IP address isn't on the allowlist for this endpoint. Contact Stellic to add it; the response includes the `client_ip` Stellic saw.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"message":{"type":"string"},"client_ip":{"type":"string"}}}}}},"404":{"description":"Section with `{id}` does not exist. A second `DELETE` on the same `{id}` also returns 404.\n\nCommon causes:\n- Section doesn't exist - returns `Course section with id:{id} does not exist`"},"500":{"description":"Unhandled server error; nothing is deleted. Returns `{\"errors\":[{\"message\":\"Something went wrong. If this issue persists, please contact a Stellic representative for assistance.\"}]}`."}}}}}}
```

#### What happens after the call

* The section is deleted right away, along with its meeting times, section details, instructors, tags, and restrictions.
* Students' section enrollments in it are deleted right away. Their course enrollments stay, so the course is still on their plan without a section.
* Students lose any permission to register for it, and other sections that named it as an auto-enroll section are left with none.
* The section's cached data and seat counts are cleared right away.

#### Notes

* **Students enrolled in the section lose that enrollment.** Enroll them in another section first with [`POST /planner/enrollment/section/{id}`](/stellic-partner-api/section-enrollment/enroll-a-student-in-a-section.md) if they should keep a section of this course.
* **Past-term sections can't be deleted.** They hold students' completed enrollments, so the call returns a 400 and nothing changes. Your data sync still manages those terms.
* **Remove the section from your feed too.** If your next data sync still carries it, the section is created again.
* **A second `DELETE` returns 404.** If "already gone" is fine for your workflow, treat that 404 as success.
* **IDs shared by more than one section return a 400.** The call won't guess which one you meant, and nothing is deleted.

#### Related APIs

* [`POST /catalog/section/{id}`](/stellic-partner-api/catalog-sections/create-a-catalog-section.md) to create a section.
* [`PUT /catalog/section/{id}`](/stellic-partner-api/catalog-sections/update-section-enrollment-caps.md) to update a section, including hiding it with `hidden` if you'd rather keep its enrollments.
* [`DELETE /planner/enrollment/section/{id}`](/stellic-partner-api/section-enrollment/remove-a-section-enrollment.md) to remove one student's section enrollment.