I took the output from the api-list_accessible_cmds API meta-command (with a key that could access everything) and used it to scaffold a basic Node.js API client.
Having the api-list_accessible_cmds command available was very handy and really made this a much more feasible project! However, it could be even better - a good chunk of the API commands get “see_docs” for all of the details:
Rather than the expected info, for example:
Is there any chance that this will be more fleshed out in the near future? Ideally, I’d like to see it have descriptions of the args and response data, and/or a link to the relevant docs. But just filling in the “see_docs” parts would be a nice improvement that could immediately be turned into an improved JS client.
Also, I designed the library to work in browsers also, and then realized you guys don’t put CORS headers on the responses. I know you wouldn’t want a key that can access everything getting exposed publicly, but I can think of a few use-cases where client-side usage with a more limited key would make sense. Is there any chance you’ll add the CORS headers?