API implementation for dabdab was quite simple. I wasn't ready to implement a full-featured api with all the niceties, because there many security and convenience related questions, however a per stream api access was a rather trivial exercise.
Some of the reasons apis are hard to work with are
I've solved the first point by not requiring api keys in the first place - a share link with api access works like a slack hook that allows to post messages with a simple post and it was ok since the url was unique.
Second point is solved by generating a real curl call that can be used to post a message. And not only that, all the values in the payload are also generated to be random.
The remaining point was about testing. The usecase for such an api is some sort of automation that gathers data from time to time and user wants to store the data somewhere and render some nice graphs. I didn't want to run a cron and used sister service webhks.com to trigger a webhook every now and that and the webhook post weather updates