> For the complete documentation index, see [llms.txt](https://docs.itoc360.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itoc360.com/integrations/inbound-integrations/error-tracking-and-uptime/statuspage.io-integration.md). # Statuspage.io Integration Atlassian [Statuspage](https://www.atlassian.com/software/statuspage) is a communication tool that lets teams publish real-time service health information to their users. It supports outbound webhook notifications whenever an incident is created, updated, or resolved — and whenever a component's operational status changes. This integration pipes those events directly into ITOC360 so your on-call team stays in the loop without having to monitor a separate status page. ### In Statuspage.io The webhook subscription lives under your page's **Subscribers** section. Navigate there from the left sidebar, then switch to the **Webhook** tab.

Click the **Options** button in the top right and select **Add subscriber**. In the modal that appears, make sure the subscriber type is set to **Webhook**, then paste your ITOC360 webhook URL into the **Endpoint URL** field.

Your endpoint URL follows this format: ``` https://api.itoc360.app/functions/v1/events?token= ``` Hit **Add subscriber** to save. Statuspage will immediately begin sending webhook payloads to that URL whenever activity occurs on your page. #### Triggering an incident To verify the integration is working, head to **Incidents** in the left sidebar and click **Create incident**. Give it a name, select at least one affected component, check **Send notifications**, and hit **Create**.

Statuspage sends a webhook for each status transition — so you will see a payload when the incident is created as `investigating`, and another when you move it through `identified`, `monitoring`, or `resolved`. #### Updating a component status Component-level status changes also trigger webhooks independently of incidents. Go to **Components** in the sidebar, find the component you want to update, and click **Edit** next to it.

On the edit screen, open the **Status** dropdown. You can set the component to any of the available states — Operational, Degraded performance, Partial outage, Major outage, or Under maintenance.

Changing the status and saving fires a `component_update` webhook event. Setting it back to **Operational** will trigger a resolve event in ITOC360. ### In ITOC360 Go to **Sources**, click **Create Source**, and select **Statuspage.io** from the list. Copy the webhook URL shown on the source detail page and use it as the endpoint when adding your subscriber in Statuspage, as described above. ITOC360 handles both event types automatically. Incident events are resolved when the incident status reaches `resolved`. Component events are resolved when the component returns to `operational`. The priority level is derived from the incident's impact field — `none` maps to Low, `minor` to Medium, `major` to High, and `critical` to Critical. Component status changes without an associated incident default to Medium priority. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.itoc360.com/integrations/inbound-integrations/error-tracking-and-uptime/statuspage.io-integration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.