Are there plans to publish API documentation for editing incident start time and component downtime?

[Johnson Earls]

The Web UI allows you to edit the start time of an incident and to edit the amount of downtime that is recorded for a component.  There are no published APIs corresponding to this functionality.

Using the browser network history, I can see one unpublished API that is used for editing component downtime, and can see that GraphQL is used for editing the incident start time, but I can't make use of unpublished APIs for a production product.

Are there any plans to publish API documentation for this functionality?

[Egor · Accepted solution]

Hey Johnson,
Thank you for reaching out and for providing detailed insight into your needs. I've gone ahead and submitted a feature request (reference: STATUS-878) for the development of API endpoints that would allow you to edit incident start times and component downtimes, similar to what you can currently do via the Web UI.

While I don’t have an immediate timeline for when this might be available, your feedback has been logged with our product team. We'll ensure you are notified if and when there's progress on this request. In the meantime, the only workaround is to manually adjust these details through the UI.

Thank you again for your valuable input! Feel free to reach out if you have any more questions or need further assistance.

Best Regards,
Egor

[Johnson Earls]

For additional information, the reason I want this is to automate both incident creation and downtime management.  because there's always the possibility that the automated system will get delayed, i want to be sure i can both create an incident with the proper start time (which backfilled incidents allow but do not allow linking to the components that are down) and to go back to a downtime that was completely missed and just retroactively apply that downtime to the component.

An alternative to both of these would be to allow incidents and incident updates to be created or updated with a date/time in the past to properly account for downtime that has already occurred.

[Egor]

Hey Johnson,
Thanks for more details! I added your comment to the mentioned ticket. 

Best Regards,
Egor