Import Status from 3rd Parties #76

Closed
opened 2026-04-05 16:18:49 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @tankerkiller125 on 2/19/2026

Is your feature request related to a problem? Please describe.
Our services at work often rely on 3rd party APIs and services, which generally do not have a public "health" endpoint we can query. While we can use the API requests to these services those requests eat into rate limits, and for some of the APIs even costs money per request made.

Something we've noticed though is that a decent chunk of these services have their own status pages, and these status pages have APIs that we can then query for the status of the specific things we want to monitor. Overall, this works pretty well on its own, but we think it can be enhanced.

Describe the solution you'd like
What I would love to see is some form of integration with these various 3rd party status page public APIs. Notably with "auto-discovery" of the available monitored services for selection in a dropdown or something.

  • Atlassian (status.company.tld/api, the /api is the docs page)
    • Cloudflare
    • Discord
    • Github
    • Twilio
    • Square
    • Reddit
    • etc.
  • Instatus (status.company.tld/summary.json)
    • Vercel
    • Linear
    • Railway
    • etc.
  • Sorry (status.company.tld/api/, like Atlassian this is the docs endpoint)
    • Popular for EU companies

Further, what would make this particularly powerful, is if the services could be configured by the Admin at a "global" level to create a "marketplace" of 3rd party status pages and components for projects to select from. The idea of this main market being that those 3rd party services could be queried one time at a global level, and the status from that global check forwarded to each individual project (reducing load out to the status page APIs).

(Further Note: Instatus has this particular feature, and it's the marketplace like design described)

Describe alternatives you've considered
Adding 3rd party status page components one at a time individually and creating API requests for each and every component.

Additional context
(All Screenshots from Instatus)
Image

Image Image
*Originally created by @tankerkiller125 on 2/19/2026* **Is your feature request related to a problem? Please describe.** Our services at work often rely on 3rd party APIs and services, which generally do not have a public "health" endpoint we can query. While we can use the API requests to these services those requests eat into rate limits, and for some of the APIs even costs money per request made. Something we've noticed though is that a decent chunk of these services have their own status pages, and these status pages have APIs that we can then query for the status of the specific things we want to monitor. Overall, this works pretty well on its own, but we think it can be enhanced. **Describe the solution you'd like** What I would love to see is some form of integration with these various 3rd party status page public APIs. Notably with "auto-discovery" of the available monitored services for selection in a dropdown or something. - Atlassian (`status.company.tld/api`, the /api is the docs page) - Cloudflare - Discord - Github - Twilio - Square - Reddit - etc. - Instatus (`status.company.tld/summary.json`) - Vercel - Linear - Railway - etc. - Sorry (`status.company.tld/api/`, like Atlassian this is the docs endpoint) - Popular for EU companies Further, what would make this particularly powerful, is if the services could be configured by the Admin at a "global" level to create a "marketplace" of 3rd party status pages and components for projects to select from. The idea of this main market being that those 3rd party services could be queried one time at a global level, and the status from that global check forwarded to each individual project (reducing load out to the status page APIs). (Further Note: Instatus has this particular feature, and it's the marketplace like design described) **Describe alternatives you've considered** Adding 3rd party status page components one at a time individually and creating API requests for each and every component. **Additional context** (All Screenshots from Instatus) <img width="1121" height="146" alt="Image" src="https://github.com/user-attachments/assets/b6478d1c-a30f-4378-bc1b-f2bba6503fa9" /> <img width="1104" height="466" alt="Image" src="https://github.com/user-attachments/assets/321bb887-9b6d-489a-8f45-67321cbcc757" /> <img width="529" height="764" alt="Image" src="https://github.com/user-attachments/assets/2559aa32-d7d7-4763-b6c4-77bc94977c27" />
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#76