Adrian Mörchen
My feedback
-
4 votes
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?
An error occurred while saving the comment Adrian Mörchen
shared this idea
·
-
12 votesAdrian Mörchen
supported this idea
·
-
30 votes
An error occurred while saving the comment Adrian Mörchen
commented
Ah okay, wasn't aware of this.
Generally still not the same. The alias itself wouldn't be "anonymous" either, as we still need to know the site.
Also, we don't want to use the alias, as we want to see the domains...
But still just want to hide the name at the public page.
Adrian Mörchen
supported this idea
·
An error occurred while saving the comment Adrian Mörchen
commented
To extend:
"Hidden URL" -> The status page is public, but the domain is just not shown.
-
11 votesAdrian Mörchen
supported this idea
·
-
3 votesAdrian Mörchen
supported this idea
·
-
337 votesAdrian Mörchen
supported this idea
·
@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]