It was only after a year of using Raindrop, the bookmarks platform, that I learned that it has an Application Programming Interface or API. And even then I didn't realize it was something I, a consumer, could use it.
I never cared for APIs. To me, they were the boring part of programming stuff, as all the do is deliver data ways so complicated that they require reading technical documentation.
I should mention, I wasn't a Raindrop fan from the start either. It just wasn't as pretty as Pocket. And the reason I started using it was that Firefox killed Pocket, which I'd used for 13 years until 2025.
But having used Raindrop for a while now, I very much appreciate how it lets me do things with my data. Mass tagging, sorting, filtering, all kinds of things that are necessary with my more than 2 200 bookmarks. Which, by the way, were over 7 000 when I started, because Pocket didn't have these features.
But even then there are things the UI doesn't let me do. Like integrating my bookmarks with my website. And that's where the API comes in.
Raindrop's API docs could be a bit clearer for novice users like myself, but all in all, it was just a fun little weekend project, getting this all set up.
And that got me thinking: with much of our data in clouds, most people depend on the graphical user interfaces to these to manage their data. If the GUI doesn't offer a certain feature, you can't really do anything about it. I've made Greasemonkey scripts to work around that, but it gave me sweaty palms when I did that with important data. APIs can be a solution where GUIs fall short.
A software-as-a-service we rely on at work has a rather limited UI and lacks features. They offer an API which could let us work around the limitations of the UI, but it costs more money. I see that a lot: only the Enterprise subscription provides an API.
But Rustem Mussabekov, the maker of Raindrop, seems like a nice person. He offers the API even to free users.
Which seems fair. By moving data from the local file system to a cloud service, users already give up so much ownership and flexibility. An API at least gives users a way to get around the limitations services create themselves.





