Every page of a status page is also available for programs and AI agents. No authentication is needed. ## Formats by Accept Header The pages and the read API answer in HTML, JSON, XML or Markdown, depending on the header `Accept` of the request. For example: ```text curl -H "Accept: text/markdown" https://statuspage.invantive.eu/en/ ``` A page in Markdown is also found by appending `.md` to its address, such as `/en/incidents/2026-0187/exact-online-netherlands-invoices-time-out.md`. A media type that is not offered gives status 406. ## Compatible with Atlassian Statuspage The following addresses answer in the shape of version 2 of the API of Atlassian Statuspage, so tools that read that format work unchanged: - `/api/v2/summary.json` - `/api/v2/status.json` - `/api/v2/components.json` - `/api/v2/incidents.json` and `/api/v2/incidents/unresolved.json` - `/api/v2/scheduled-maintenances.json`, `/api/v2/scheduled-maintenances/upcoming.json` and `/api/v2/scheduled-maintenances/active.json` ## Feeds The incidents and maintenance of a page are available as a feed at `/en/feed.atom`, `/en/feed.rss` and `/en/feed.json`. A feed of a component, an incident or a month is found by appending `.atom` or `.rss` to its address. ## Files for Search Engines and Agents Every page offers `/robots.txt`, `/sitemap.xml`, `/llms.txt` and `/.well-known/security.txt`. The pages carry structured data for search engines. ## Further Interfaces The live state is available as `/api/v1/state` and the state for the [[Invantive Cloud Status/Public Pages/Widget|widget]] as `/api/v1/widget.json`. Changing the status from a program is described in [[Invantive Cloud Status/Interfaces/Management API|Management API]].