Skip to main content
Question

Help with Docebo User API Integration via OAuth2

  • April 3, 2025
  • 1 reply
  • 121 views
A

Hi everyone – I’m a brand new Docebo user and really appreciate this community!

We’re currently setting up an integration between Docebo and our external site. OAuth2 authentication is working—we’re able to obtain the access token successfully. Now we’re trying to use the Docebo User API to retrieve user information (like user ID, name, and email) using that token, so we can sync the data on our external platform.

Here’s a sample OAuth2 token response we’re getting from Docebo:{"access_token":"ACCESS_TOKEN_VALUE_HERE","expires_in":3600,"token_type":"Bearer","scope":"api","refresh_token":"REFRESH_TOKEN_VALUE_HERE"}

As you can see, the response doesn’t include any user information (like user ID), so we’re not sure how to proceed with retrieving user details using the access token.

Has anyone successfully done this kind of integration? Specifically:

  • Which API endpoint(s) should we use to get user info using the access token?

  • Any tips on best practices for securely syncing Docebo user data with an external site?

Any help or examples would be hugely appreciated. Thanks so much in advance!

    1 reply

    hailey.gebhart
    Helper III

    From what I can see in your post, it looks like you are authenticating yourself, but not calling the endpoints that have information after you have completed authentication. Which endpoints are you using that is giving you that response, if it is only the OAuth2 authentication, that is why you are not seeing any user data.

    Once you have authenticated like you showed above, you need to add that token to your headers, like this:

    headers = {
    'Authorization': 'Bearer {TOKEN}',
    'Accept': 'application/json'
    }

     

    Then you need to change your URL to the actual endpoint you are trying to use, such as 

     

    https://learn.your-docebo-url-here.com/manage/v1/user/{user_id}

    So this url is what you would submit with the headers formatted like the brackets above. If you are using a service such as Postman, they make it easy to see your headers/auto-authenticate. Postman can also provide the code in various coding languages to get it set up if you are taking the manual route.

     

    If you are using a different endpoint after you receive your token, it may be due to the response body parameters you have set or whatever you are looking at is not the actual response body of your API call.

     

    Let me know if any of this helps, or if there are more details you can provide, so I can be of more assistance!

    Terms & ConditionsCookie settingsAccessibility statement