A huge drawback (for me) of using APIs is that 95% of the endpoints want some ID that isn’t easily visible. Usually you have go to a different API to retrieve it. There are some endpoints in the API browser, like "Returns list of mappable fields for the data importer" under Manage > Users that just 'dump' info. This is very helpful.
This leaves me with two questions
1. Somewhat rhetorically - How come Docebo has hamstrung us like this? Why not have a series of standard endpoints, themselves organized collectively instead of hidden all over the place, that provide the basic ID for all catalogs, all learning plans, all courses, all training materials, all sessions, all events, etc. This api-browser holds so many endpoints, many that I can't imagine ever using...but the simple, low hanging tasks are almost impossible to do.
2. So, assuming that I can happen upon a list of IDs that I want to use, how do I keep that information so that I don't need to figure out how to find it again? For example, I find a list of catalog IDs. What's the best practice? Scrape off the .json and then convert it to .csv?
Best answer by Bfarkas
View original