Skip to main content
Question

API to fetch all course enrollments for a specific user by UUID

  • April 7, 2026
  • 1 reply
  • 7 views

I am looking for an API that takes a user's UUID as input and returns all the courses they are enrolled in, along with the enrollment status (subscribed / in_progress / completed).
We have tried the following endpoints but none gave the right output:

GET /report/v1/mytranscript — returns data for the currently authenticated user only, does not accept a UUID to fetch another user's data
GET /course/v1/courses/enrollments — permission denied even when called with an admin token
GET /analytics/v1/dashboard/branches/users/list — returns all users in a branch, cannot be filtered down to a single specific user

Is there an official endpoint that accepts a user UUID and returns their complete enrollment list with course details and status? Any help or workaround is appreciated.

1 reply

Moshe.Machlav
Helper III
Forum|alt.badge.img+1

In organizations I've worked with, trying to pull a complete enrollment list user-by-user via synchronous APIs becomes a major performance bottleneck, which is exactly why Docebo doesn't expose a single 'UUID-to-Enrollments' endpoint.

Before diving into a multi-step API workaround, I'm curious: why are you trying to extract this programmatically rather than using the built-in platform features?

If the goal is simply to view a specific user's enrollments and statuses, you can generate a User Personal Summary directly from the admin menu. This built-in report gives you exactly what you're looking for, a full view of every course the user is enrolled in, along with their current status without needing to write any code.

You can check the documentation on how to pull that summary here: https://help.docebo.com/hc/en-us/articles/360020125699-Generating-a-User-personal-summary-report

If you are pulling this data to feed into an external system, what system are you integrating with? Depending on the destination, using a Docebo Connect recipe (which handles the API ID mapping automatically) or setting up an automated CSV report export is usually a much more stable approach than querying the API user-by-user.

Let me know a bit more about the end goal, and we can point you in the right direction.