I’m very excited about this, since the repeated increased security measures keep breaking the auth for the extremely hacky (but very extensive and used daily by many people) integration I’ve set up for intend.do: WorkFlowy ↔ Intend
However! In order to get this working, I’ll need the ability to get the entire tree, with children. Frankly if you’d be willing to expose the existing root endpoint, that returns the ch: […childnodes…] arrays included as a full tree, and with notes as no, name as nm, lastModified as lm, just like it is on your existing backend, then I could just plug it in without having to refactor my backend to use different keys. And honestly that might make sense because returning JSON with these longer keys is probably going to be somewhat bigger.
But yeah, my integration relies on getting the FULL tree, since it scans it all for things tagged to link to my app—so while I’m excited, I’m not even going to attempt to use this rudimentary API by recursively sending a new request for child nodes for each node. That’d be ridiculous for even a moderately-sized graph, never mind my 15MB one. (Also when I briefly tested GET /nodes/:id it seemed to only return the node itself, without any children!)
Also, why not already allow users to generate multiple API keys marked with different names, so you can give different ones to different apps and thus easily de-auth the apps. That’s not hard at all. (Compared to setting up full-on OAuth)
Anyway please please please more of this. There is so much possible via integrating with workflowy!