API
Workflowy does not yet have an official API available.
We definitely plan on building one, but it isn't at the top of our priorities and we don't have an estimate for when we'll do it.
However, there is an unofficial API written by one of our users in PHP:
-
Hi there,
I'm currently playing a bit with the API for a little pet project, taking both the workflowyPHP library and this node library as starting points.
I've noticed that a few things seem to have changed: notably, a 'castle_client_id' is now required (I guess it's for castle.io) to successfully use the endpoint to log in.
I just wanted to check: is it still fine to (respectfully) play with the API? Are there other channels you'd prefer to communicate/discuss things? (I remember someone mentioning they exchanged some friendly and helpful messages with developers)
Regarding my API experiments: re-using some castle_client_id generated in the browser seems to do the trick, but I'm wondering how likely this is to break? If this is indeed for castle.io, should I play nice and generate random compliant IDs? I'm using my own paid account and don't want to get banned either :)
Kindly,
Julien -
Hi Julien!
You can reach out to developers directly via the Slack group and see what you can glean:
https://join.slack.com/t/workflowyusergroup/shared_invite/zt-s867uw4j-hxIqSvU7n6e7gXKwpjVWbw
You can tag @jay or @anatoliy :-)
-
Hi Alex!
Here's an update:
https://join.slack.com/t/workflowyusergroup/shared_invite/zt-s867uw4j-hxIqSvU7n6e7gXKwpjVWbw
Please sign in to leave a comment.
Comments
67 comments