I’ve been an Admin for a Docebo instance for a few months now and am learning my way around the APIs. One of my first challenges was to build a solution to update users in Docebo from our HR data. I had been running my solution for a week and validating that changes to users were being made via my python scripts. Then I started seeing users with first and last name changes that were not being updated by my code.
My code was retrieving the existing users and comparing their fields against an employee id we store as an additional field. When the values in Docebo don’t match HR, my code simply changes the value of the Docebo user object using the field key. What I learned is that field keys for requesting users do not always match field keys when you need to update users.
From the API Documentation, I discovered that user’s first name and last name object keys are different for GETs than POSTs and PUTs.
| GET User Object Response Keys | PUT/POST User Object Payload Keys |
| first_name | firstname |
| last_name | lastname |
| is_manager | can_mange_subordinates |
Has anyone else found these inconsistencies frustrating?
How have you addressed it?
Are there more?
Let’s discuss!