Skip to main content
Question

Updating Additional Fields For Users Via API

  • March 19, 2026
  • 2 replies
  • 39 views
P

Hello.  I just inherited Docebo from our guru that left the company and there was a project in flight to update one of the APIs that add/update/inactivate user data.  Docebo is new to me and I am semi-technical.  We have a few APIs doing this for different groups (employees, contractors, etc.).  I am still getting information, but my understanding is that our IT group updated the API with the new field but it isn’t populating in the system.  Does anyone have any advice on if there is something else that needs to be “mapped” somewhere or anything else that might be helpful in adding a new additional field to an exist user API?  Thanks in advance.

2 replies

dwilburn
Guide III
Forum|alt.badge.img+5
  • dwilburn
  • Guide III
  • March 20, 2026

Hi ​@PonzioC - your first check would need to be asking IT for any error messages from the API, and what API call they are making. This is key to understanding what steps to take next.

Regarding testing what should be occurring, that may take a bit of effort. Info below.

You can go into the API browser for your system (https://<yourdomain>.docebosaas.com/api-browser/ and then test to replicate the API call and see the errors.

If you can invest several hours, the workshop below can get you well on the way of understanding the API in Docebo, how to test with the API browser, and how to use postman.

​@Bfarkas did a great series of workshops to help users get comfortable with the API, the API Browser, and Postman.

https://community.docebo.com/events?tab=past&type=Virtual%20Workshop

In the API browser, where Services = Manage, then Users, there are calls for creating and updating users.

All of the documentation is there in the API browser. ChatGPT / CoPilot can be handy here, guiding you through rough spots, but they are not always current on the latest changes to the API.

Hope this helps.

    P
    • PonzioC
    • Author
    • Newcomer
    • March 24, 2026

    Thanks.  That is all very helpful.  What is baffling me is that this was apparently already working and all we did was add the new field but it isn’t populating into the system.  I’m told we’re not getting an error though.

     

    I’m wondering there is something simple in the configuration, etc. that needs to be turned on, etc., to allow the field to be written to (?).

     

    Any thoughts are appreciated.

     

    {

        "userid": "GRNPW0000XXXX",

        "email": "johndoe@email.com",

        "password": "randompassword",

        "firstname": "John",

        "lastname": "Doe",

        "force_change": 0,

        "level": 6,

        "valid": 1,

        "additional_fields": {

            "2": null,

            "3": null,

            "4": "XXX-XXX-XXXX",

            "5": "Location",

            "6": "2024-08-30",

            "7": null,

            "10": null,

            "14": null,

            "15": null,

            "16": null,

            "17": null,

            "28": "New Value"

        }

    }

    Terms & ConditionsAccessibility statement