Whatever happened to programmable web?
https://en.wikipedia.org/wiki/ProgrammableWeb - "was an..." Bummer.
A Collection of Free Public APIs That Is Tested Daily
71–80 of 130 posts
Re: A Collection of Free Public APIs That Is Tested Daily
#72I tried to build something years ago on a similar foundation, and I found maintaining the API list to be impossible as a solo dev. In a pool of say 30 APIs, at least one would break their "contract" as a public resource daily. Shifting endpoints, revoked public tokens, changing outputs. I was quite disappointed because I loved the product, a dashboard for arbitrary live data sourced from APIs, but the cost of maintai…
Of course I assume there is documentation that is updated before new changes go live which might be too much to ask :)
Re: A Collection of Free Public APIs That Is Tested Daily
#73Earlier quoted context omitted.
What I really want is isoddapi.xyz. Just like the npm package, all it should do is call isevenapi.xyz and invert the result.
I'd like to see isfizzbuzz.xyz. Ideally, before 11:30 AM ET this Friday.
Cheers!
Re: A Collection of Free Public APIs That Is Tested Daily
#74Tangentially, what APIs do you guys actually pay for? (Personally or through work)
Re: A Collection of Free Public APIs That Is Tested Daily
#75An API for polling data would be cool, one can dream
Not so much for polling data, but some governments do allow access to coarse election data. Australia's was enough that the unfortunately complicated math of their election system was repeatable and verifiable (Can't find the post about it, however)
Re: A Collection of Free Public APIs That Is Tested Daily
#76Re: A Collection of Free Public APIs That Is Tested Daily
#77Re: A Collection of Free Public APIs That Is Tested Daily
#78(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…
> Running an API Forwarder that could act as a common target for all your APIs might work.
That just sounds like adding another point of failure into the chain.Re: A Collection of Free Public APIs That Is Tested Daily
#79(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.
> having made the mistake of using a public API (that later went offline) for examples in a book of mine
Literally a tale as old as time. The Old Testament references a command from God, that is not contained in the Old Testament itself.