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.
Maybe you could! Perhaps a sample data API that creates users like "John Chocolate Oreos," address "100 Pack Street", age 19.99, email "visit<at>oreo.com"
I don’t think Oreo would want to commit ad spend to that—it would perform worse than the display network, and worse than the Outbrain/Taboolas of the world.
(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.
I did a similar deep dive to find all the specifically Music-related APIs that are available a few years ago. I've since moved on to other projects but maybe someone will find it useful / maybe OP can add the entries in my list to FreePublicAPIs.com!
These come in handy in an instructional context—being able to have a simple predictable API that you can point students at so they can learn how to call an API and process its data.
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.
Readit News
Maybe you could! Perhaps a sample data API that creates users like "John Chocolate Oreos," address "100 Pack Street", age 19.99, email "visit<at>oreo.com"
These days I keep an API deployed on a subdomain I control.
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.
https://docs.sweeting.me/s/music-apis
Best part is that 'sign up' links to https://archive.org/donate/
API Result:
GET https://api.isevenapi.xyz/api/iseven/6/
{"ad":"Buy isEvenCoin, the hottest new cryptocurrency!","iseven":true}
Just like the npm package, all it should do is call isevenapi.xyz and invert the result.
Ideally, before 11:30 AM ET this Friday.
Deleted Comment
I'm not saying these shouldn't exist, I think they're pretty funny, but everything in its place.
Deleted Comment
Deleted Comment
Dead Comment
Dead Comment
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.
Hence testing them daily to see if the someone else is still offering them.
Not all abstractions are leaky. Not at all.