The wrappers aren’t really needed because the API is very simple.
Granted, it isn’t easy to use until you understand how REST works, and how to setup the parameters and handle the results, but the wrappers are a convenience that will get in the way of understanding the API until you understand the language the wrapper is written in.
My code is clunky as a result, and I’d like to refactor it at some point as I’m getting a bit more skilled, but it works.
Start by looking at safestoreAuthorize(), which obtains a token using the /auth API.
Then look at the other places I call the API - hint: search for calls to _request.
Also, if you look at the _request() function itself, notice how it inserts the token obtained by safestoreAuthorize() into the headers for each HTTP request.
You can ignore most of the code around the calls to the API and just look at how I call each API by setting up the call to do the HTTP requests, and how I interpret the results returned by them.
I don’t have much time to explain what the code is doing (and most of it is irrelevant to you seeing how I use the SAFE API) but will try to answer questions that are not too involved - don’t expect instant replies though because I’m juggling several things ATM (not software)