Feature Requests JSON version of the status page
Under Review
Having a JSON version of the status page allows any possible integration with 3rd party tools/dashboards. Lowers the amount of API requests required to get similar content (even though I think not all of the information that is currently visible on the status page is also available using the existing API). Probably you want to put it behind the API key except maybe for public status pages.
Bram
Created on July 02, 2020 · Last update on August 17, 2024
3 Comments
Thanks for the suggestion, this is something which have been asked a couple times in the past and is under review for the roadmap.
Quick question: if this is for website which have a public status page, how would you feel about a public (no api key) read-only API for them?
Or do you prefer one read-only API key per check?
@Adrien ;)
A public read-only API for the public status page would be totally fine. The websites are online (and public) anyway.
I just need a way to grab "structured data" at client sites without exposing all other checks [through a single API key]
Sign in to comment