> For the complete documentation index, see [llms.txt](https://help.sleuth.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sleuth.io/sleuth-dora/integrations-1/impact-sources/incident-tracker-integrations/statuspage.md).
# Statuspage
## About the integration 
Statuspage can easily communicate real-time status to your users. Integrating Statuspage with Sleuth is simple using an API token.
## Setting up the integration
To add the Sleuth Statuspage integration:
* Click **Integrations** in the sidebar.
* Click the *Incidents* tab, then **add** in the *Statuspage* card.
* Enter your API token
* Press **Save**.
## Configuring the integration
* Click **Add incident source** and select a Sleuth project that will track Statuspage incidents. All projects within your organization will be displayed in the dropdown.
* Configure impact source by mapping incidents Statuspage's page and component to Sleuth environment.
* Under advanced settings, you can control the historic data population. If checked Sleuth will populate all incidents that happened in the last 30 days and recalculate the project's Failure Rate and MTTR metrics.
{% hint style="info" %}
Integrations are made at the Sleuth organization level and are available for all projects within that organization. Individual settings for integration are made at the project level.
{% endhint %}
* That's it! Sleuth will now start tracking incidents for pages and components declared in Statuspage.
---
# 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://help.sleuth.io/sleuth-dora/integrations-1/impact-sources/incident-tracker-integrations/statuspage.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.