Live data from Hacker News

A Collection of Free Public APIs That Is Tested Daily

freepublicapis.com

11–20 of 130 posts

Re: A Collection of Free Public APIs That Is Tested Daily

#12

Paraphrasing a known saying, "there's no API, it's just someone else's computer". I wish programmers would internalize this. They often seem to take APIs uncritically, not questioning whose resources they're using and where does the data come from as well as its quality beyond obvious cases. APIs are leaky abstractions as all abstractions are.

API doesn't mean someone's else's computer.

Re: A Collection of Free Public APIs That Is Tested Daily

#15
The key here is tested daily. The last time I wanted some sample data api it took me way too long to find one because all the ones that were recommended to me were deprecated. It's really tough to keep a free api up, because there's no incentives. You can't sell ads on it.

Re: A Collection of Free Public APIs That Is Tested Daily

#17

Paraphrasing a known saying, "there's no API, it's just someone else's computer". I wish programmers would internalize this. They often seem to take APIs uncritically, not questioning whose resources they're using and where does the data come from as well as its quality beyond obvious cases. APIs are leaky abstractions as all abstractions are.

APIs can be hosted locally. In fact, I think most of them are.

Re: A Collection of Free Public APIs That Is Tested Daily

#18
post #15

The key here is tested daily. The last time I wanted some sample data api it took me way too long to find one because all the ones that were recommended to me were deprecated. It's really tough to keep a free api up, because there's no incentives. You can't sell ads on it.

> You can't sell ads on it.

Maybe you could! Perhaps a sample data API that creates users like "John Chocolate Oreos," address "100 Pack Street", age 19.99, email "visitoreo.com"

Re: A Collection of Free Public APIs That Is Tested Daily

#19
post #3

(This doesn't apply to every API in the list, but) having made the mistake of using a public API (that later went offline) for examples in a book of mine, never again. These days I keep an API deployed on a subdomain I control.

The possibility of an internet resource disappearing exists regardless of the resource type. Running an API Forwarder that could act as a common target for all your APIs might work. Give it the request, and it passes it on, records success, optionally sends a notification if an endpoint that previously succeeded is now failing.

Add a fancy feature of redirection with format changing to handle replacing dead APIs with new ones transparently.

If anybody makes one of these, they should totally make it a free public API. I'd use it, and I'm not certain if that would just be ironically.

Post reply on HN