Adding per-incident routes on statuspage public api

[Digital 39999]

If we're for example checking the status page by fetching the summary endpoint, as known there are only active incidents, so for example if one is made, and we have some app that checks that, and stores the incident id, and then checks if it has been resolved or deleted, its a little hard to know which happened because item is just directly removed from the array. To find out of it has been deleted we would need to fetch whole list of all ever incidents which increased bandwidth a lot if done for multiple pages. So, it would be nice having some endpoint like /api/v2/incidents/id.json to check if it has been resolved and with what data or deleted.

[Egor · Accepted solution]

Hi There, 
Welcome to Atlassian Community!

Thank you for bringing up this suggestion! I’ve created an internal feature request to track your idea (STATUS-916). This enhancement is indeed a valid and valuable option, as it would simplify incident tracking and reduce bandwidth usage, especially for users managing multiple pages.

While feature requests are now tracked internally and aren’t publicly accessible, I assure you that your input has been shared with the relevant team for review. Atlassian evaluates feature requests based on user impact, feasibility, and alignment with product goals during our planning cycles.

Although I can’t provide a specific timeline for implementation, we appreciate your feedback, as it helps us improve the product for all users. Please feel free to reach out if you have additional thoughts or need assistance with anything else.

Thank you again for your contribution!

Best Regards,
Egor