---
title: "Deactivate course"
method: POST
path: "/lms/courses/{course_id}/deactivate"
tags: ["Unified LMS API"]
---

# Deactivate course

`POST /lms/courses/{course_id}/deactivate`

Deactivate a course in the LMS.

Deactivates a course, making it unavailable for new enrollments while preserving existing progress records.

<Note>
  This endpoint requires the permission **Upsert courses** to be enabled in [your scope config](/scopes).
</Note>

## Path parameters

- `course_id` string, required — The ID of the course in Kombo or its ID in the remote system by prefixing it with `remote:` (e.g., `remote:12312`)

## Headers

- `X-Integration-Id` string, required

## Request body

- PostLmsCoursesCourseIdDeactivateRequestBody

## Response `200`

POST /lms/courses/:course_id/deactivate Positive response

- PostLmsCoursesCourseIdDeactivatePositiveResponse
  - `status` 'success', required
  - `data` object, required
    - `id` string, required — The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing.
    - `remote_id` string, required — The raw ID of the object in the remote system. We don't recommend using this as a primary key on your side as it might sometimes be compromised of multiple identifiers if a system doesn't provide a clear primary key.
    - `provider_id` string, nullable, required — The Kombo ID of the course provider of this course, if applicable.
    - `origin_id` string, nullable, required — A stable identifier you provided when creating this course. Can be used to identify and update the course in subsequent requests.
    - `remote_created_at` string, date-time, nullable, required — The date and time the object was created in the remote system.
    - `remote_deleted_at` string, date-time, nullable, required — The date and time the object was deleted in the remote system. Objects are automatically marked as deleted when Kombo can't retrieve them from the remote system anymore. Kombo will also anonymize entries 14 days after they disappear.
    - `changed_at` string, date-time, required — The timestamp when this specific record was last modified. This field only updates when properties directly on this record change, NOT when related or nested models change. For filtering that considers nested data changes, use the `updated_after` parameter which will return records when either the record itself OR its related models have been updated.
    - `remote_data` object, nullable, required — Includes the data fetched from the remote system. Please be aware that including this in you scope config might violate other scopes that are set. Remote data always has the endpoint path that we got the data from as the top level key. For example, it could look like: `{ "/companies": { ... }}` This is not available on all plans. Reach out to Kombo if you need it.
    - `custom_fields` object, nullable, required — A key-value store of fields not covered by the schema. [Read more](/custom-fields)
    - `integration_fields` object[], required — An array of selected passthrough integration fields. [Read more](/integration-fields)
      - `id` string, required — The globally unique ID of this object.
      - `key` string, required — The key of the field in the remote system.
      - `type` 'DEFAULT' | 'CUSTOM', required — - `DEFAULT`: static fields in the remote system. - `CUSTOM`: fields that are created/editable by the user.
      - `value` unknown
      - `label` string, nullable, required — The label of the field. (not always available)
    - `provider` object, nullable, required
      - `id` string, required — The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing.
      - `remote_id` string, required — The raw ID of the object in the remote system. We don't recommend using this as a primary key on your side as it might sometimes be compromised of multiple identifiers if a system doesn't provide a clear primary key.
      - `name` string, nullable, required — The name of the provider.
    - `revisions` object[], required
      - `id` string, required — The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing.
      - `remote_id` string, required — The raw ID of the object in the remote system. We don't recommend using this as a primary key on your side as it might sometimes be compromised of multiple identifiers if a system doesn't provide a clear primary key.
      - `course_id` string, nullable, required — The Kombo ID of the course this revision belongs to. The ID can be used to retrieve the course from the `get courses` endpoint.
      - `title` string, nullable, required — The title of the course revision.
      - `description` string, nullable, required — A description of the course revision.
      - `remote_url` string, nullable, required — URL to the course overview page within the LMS itself.
      - `status` 'ACTIVE' | 'INACTIVE', nullable, required — The status of this revision (ACTIVE or INACTIVE).
      - `remote_created_at` string, date-time, nullable, required — The date and time the object was created in the remote system.
      - `remote_deleted_at` string, date-time, nullable, required — The date and time the object was deleted in the remote system. Objects are automatically marked as deleted when Kombo can't retrieve them from the remote system anymore. Kombo will also anonymize entries 14 days after they disappear.
      - `changed_at` string, date-time, required — The timestamp when this specific record was last modified. This field only updates when properties directly on this record change, NOT when related or nested models change. For filtering that considers nested data changes, use the `updated_after` parameter which will return records when either the record itself OR its related models have been updated.
      - `remote_data` object, nullable, required — Includes the data fetched from the remote system. Please be aware that including this in you scope config might violate other scopes that are set. Remote data always has the endpoint path that we got the data from as the top level key. For example, it could look like: `{ "/companies": { ... }}` This is not available on all plans. Reach out to Kombo if you need it.
      - `custom_fields` object, nullable, required — A key-value store of fields not covered by the schema. [Read more](/custom-fields)
      - `integration_fields` object[], required — An array of selected passthrough integration fields. [Read more](/integration-fields)
        - `id` string, required — The globally unique ID of this object.
        - `key` string, required — The key of the field in the remote system.
        - `type` 'DEFAULT' | 'CUSTOM', required — - `DEFAULT`: static fields in the remote system. - `CUSTOM`: fields that are created/editable by the user.
        - `value` unknown
        - `label` string, nullable, required — The label of the field. (not always available)
      - `skill_assignments` object[], required
        - `skill` object, required
          - `id` string, required — The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing.
          - `remote_id` string, nullable, required — The raw ID of the object in the remote system. We don't recommend using this as a primary key on your side as it might sometimes be compromised of multiple identifiers if a system doesn't provide a clear primary key.
          - `name` string, nullable, required — The name of the skill.
  - `warnings` object[], required — These are the interaction warnings that are shown in the dashboard. They are meant to provide debug information to you. We recommend logging them to the console.
    - `message` string, required

## Other responses

- `default` — The standard error response with just the platform error codes.

---

[API](https://skmtc.net/kombo/apis/kombo-api.md) · [All operations](https://skmtc.net/kombo/apis/kombo-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/kombo/kombo-api/versions/1e45035b96d3/schema)