cURL's API is the best out there.
Ask HN: Which is your most favorite API?
21–24 of 24 posts
Re: Ask HN: Which is your most favorite API?
#22Spotify API - well documented, straight foward to use, and has made it easier for manage my library and make playlists for myself.
As someone who doesn't use APIs frequently, how does your interaction with Spotify's API differ from interacting with the app?
Example:
- Get a list of your 10 most listened artists
- For each artist get 5 similar artists
- Now make an new playlists, and for the 50 similar artists, get their most popular song and insert it into the playlist
Re: Ask HN: Which is your most favorite API?
#23Imgix is really fun to use.
Cloudflare Workers are awesome to work with.
Re: Ask HN: Which is your most favorite API?
#24Flickr's API is still the best. Does everything you want it to. Has a few fun surprises that you didn't expect that make it even more fun to make things with. Simple to use. Well documented. Test playground at your fingertips to experiment with any call you like. One of the first APIs ever released and you can still count the number of other available APIs that positively compare on one hand.
Can you give examples of those fun surprises? I'm curious. Thanks!
One of the fun things you can do is using the set of places API methods.
flickr.places.findByLatLon returns a placesId based on a supplied lat/long of somewhere you might be interested in.
You can then use that placeId to get photos around that location with a call to flickr.places.getChildrenWithPhotosPublic
Even more amusing is that you can get the actual shape co-ordinates for that place (for example the shape values or the polyline values of your local suburb or city).
I can tell you that I didn't expect to be able to access the shapefiles, bounding boxes and polylines for essentially every suburb I needed for a location based app I was building 10 years ago from a photo app API.