Skip to main content
Question

Docebo API endpoint that returns observation checklist results (not just completion status)?

  • May 18, 2026
  • 2 replies
  • 17 views


Hi all!

Hoping someone here has figured this out because I'm going in circles a bit!

We have observation checklists being completed in Docebo and I want to get the results automatically emailed to our power users on a schedule — so they can actually see what's going on without having to log into the platform.

I've already poked around in the checklists dashboard and the API browser, and I'm building a Power Automate flow to try and pull this off. But I'm hitting a wall figuring out which API endpoint actually returns the checklist response data (not just whether it was completed or not).

A few things I'd love to know:
1. Has anyone pulled observation checklist results through the API? Which endpoint worked for you?
2. Are you using Power Automate for this or something else entirely?
3. Any weird quirks I should know about before I go too far down this path?

Really open to however people are solving this — just want the results landing in inboxes on a regular basis without it being a manual process every time. Thanks!

2 replies

Moshe.Machlav
Guide I
Forum|alt.badge.img+1

Hi ​@kenny.sakun,

You are going in circles because the endpoint you are looking for doesn't actually exist. You aren't missing anything, Docebo's public APIs (and webhooks) currently only expose the Completion Status and the final score of an observation checklist, not the line-by-line responses.

If your primary goal is to get the actual granular answers emailed automatically to power users without them logging in, you might need to bypass the native Docebo checklist entirely.

The Alternative Approach: Have you considered embedding a Microsoft Form, Google Form, or Typeform directly into the course as a training material? By doing this, you can use your existing Power Automate setup to trigger an email containing all the exact responses the second the form is submitted.

If you absolutely must use the native Observation Checklists for manager/observer workflows, the data extraction becomes much more limited. When I've deployed this for organizations with similar requirements, we often hit this exact wall. The compromise is usually either:

  1. Setting up a scheduled flow (via Power Automate, Workato, or n8n) to pull the Completion Status of recently finished checklists and emailing managers a prompt to "Log in to view the new submission details."

  2. Switching to an embedded external form to prioritize the automated data extraction.

For more foundational context on what is supported natively, you can reference the official documentation here: Creating observation checklists – Docebo Help

I know it's not the magic endpoint you were hoping for, but I hope this saves you from spending more hours digging through the API browser!


mj_
Docebian
Forum|alt.badge.img+2
  • Docebian
  • May 20, 2026

Ciao, ​@kenny.sakun 👋

To pull observation checklist responses via API, you will want to take a look at the “Get An Assignment With The Relative Answers” GET /otj/v1/assignments/{assignment_id}.

The trickiest part is getting the assignment ID, which uniquely identifies a submission of a checklist. To do this programmatically using a tool like Power Automate, you might consider using one of the observation checklist webhooks in Docebo. Once set up, when a user completes a checklist:

  1. A webhook automatically sends that information (including the assignment id) from Docebo to your specific Power Automate workflow.
  2. Power Automate uses that assignment ID to call the API above to get the checklist responses.
  3. Power Automate as part of the workflow can clean up the data to make it more presentable to be emailed.
  4. Power Automate emails the power user.

This works if you want to send emails one by one as checklists are completed. If you would like to send multiple responses at the end of each day or week, then instead of performing step 4 immediately, store that information in a table in Power Automate instead, then set up a separate workflow that runs on a schedule to collect all responses from the table and send them in one go.