---
title: "Check course progression"
method: POST
path: "/lms/check-course-progression"
tags: ["Unified LMS API"]
---

# Check course progression

`POST /lms/check-course-progression`

Check in real time whether a user is enrolled in a course and read their progression.

Answers the question "is this user enrolled in this course?" by querying the remote system directly, bypassing the data from the most recent sync. Use this when you need an authoritative enrollment check without waiting for the next sync.

### Example Request Body

```json
{
  "user_id": "7xPdr68N8kG9EzLwjsN9xyz",
  "course_id": "26vafvWSRmbhNcxJYqjCzuJg"
}
```

## Headers

- `X-Integration-Id` string, required

## Request body

- PostLmsCheckCourseProgressionRequestBody
  - `user_id` string, required — The ID of the user in Kombo or their ID in the remote system by prefixing it with `remote:` (e.g., `remote:12312`).
  - `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`).

## Response `200`

POST /lms/check-course-progression Positive response

- PostLmsCheckCourseProgressionPositiveResponse
  - `status` 'success', required
  - `data` object, required
    - `is_enrolled` boolean, required — Whether the user is currently enrolled in the course according to the LMS.
    - `course_progression` object, nullable, required — The user’s course progression, fetched in real time from the LMS. `null` when the user is not enrolled.
      - `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.
      - `user_id` string, required — The Kombo ID of the user this progression relates to. The ID can be used to retrieve the user from the `get users` endpoint.
      - `course_revision_id` string, required — The Kombo ID of the revision this progression relates to. The ID can be used to retrieve the revision from the `get courses` endpoint.
      - `status` 'ENROLLED' | 'IN_PROGRESS' | 'COMPLETED' | 'DROPPED', nullable, required — Current status of the learner in this course revision.
      - `enrolled_at` string, date-time, nullable, required — Date when the user enrolled in the course revision.
      - `completed_at` string, date-time, nullable, required — Date when the user completed the course revision.
      - `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_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.
      - `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.
      - `user` 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.
        - `first_name` string, nullable, required — The user's first name.
        - `last_name` string, nullable, required — The user's last name.
        - `work_email` string, nullable, required — The user's work email address.
      - `course_revision` 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.
        - `title` string, nullable, required — The title of the course revision.
        - `course` 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.
  - `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/revisions/149bf44faf1a/schema)