> 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/statuscake-integration.md).

# StatusCake Integration

[StatusCake](https://www.statuscake.com/) is an uptime and performance monitoring tool that tracks whether your websites, APIs, and servers are reachable. When a monitored endpoint goes down or comes back up, StatusCake can notify any webhook URL you configure — including ITOC360.

This integration connects StatusCake to itoc360 through a Contact Group. Every time a test fails or recovers, ITOC360 receives the alert automatically and creates or resolves the corresponding incident.

### How It Works

StatusCake sends an HTTP POST request with form-encoded data to your ITOC360 webhook URL whenever a test changes state. The `Status` field in the payload tells ITOC360 whether the endpoint is `DOWN` (open an incident) or `UP` (resolve it). The combination of test name and URL is used to match open and resolved incidents together.

### Prerequisites

* A StatusCake account
* Your ITOC360 webhook URL, generated when you create the integration

### In ITOC360

Go to **Sources**, click **Create Source** , and select **StatusCake** from the list. Copy the webhook URL that appears — you'll need it in the next step.

### In StatusCake

#### Step 1 — Create a Contact Group

In the left sidebar, go to **Alerting → Contact Groups**, then click **New Contact Group**.

Fill in the form as follows:

* **Group Name** — give it a recognizable name, like `itoc360`
* **Enable Repeat Alert** — leave this disabled (the toggle should show "Disabled")
* **Webhook URL** — [https://api.itoc360.app/functions/v1/events?token=\<x-itoc360-token>](https://api.itoc360.app/functions/v1/events?token=<x-itoc-360>)
* **Webhook Request Method** — select **POST**

You can ignore the Email and SMS fields.

<figure><img src="/files/ck5igoFdb9VFZbzGoncL" alt=""><figcaption></figcaption></figure>

Click **Save Contact Group**.

#### Step 2 — Create an Uptime Test

In the left sidebar, go to **Monitoring → Uptime**, then click **New Uptime Test** on the right side of the page.

<figure><img src="/files/QhLQiitPEkSEGMUhpkcI" alt=""><figcaption></figcaption></figure>

Fill in the test details:

* **URL** — the endpoint you want to monitor ([https://api.itoc360.app/functions/v1/events?token=\<x-itoc-360>](https://api.itoc360.app/functions/v1/events?token=<x-itoc-360>))
* **Test Name** — a descriptive name for the test
* **Who to Alert (Contact Groups)** — select the Contact Group you created in Step 1 (e.g. `ITOC360`)
* **Check Rate** — choose how often StatusCake should check the endpoint; **15 MIN** is a reasonable default for most use cases

<figure><img src="/files/67aYUXf2AmurQBsEEP06" alt=""><figcaption></figcaption></figure>

Scroll down and click **Create Test**.

<figure><img src="/files/GimYYh09IEKq7MJiNkuE" alt=""><figcaption></figcaption></figure>

### Alert Behavior

| Status | itoc360 Action                 |
| ------ | ------------------------------ |
| `DOWN` | Opens a new incident           |
| `UP`   | Resolves the existing incident |

StatusCake identifies which test triggered the webhook using the test name and monitored URL — ITOC360 uses these together as the incident fingerprint, so open and resolved events are always matched correctly.

### Notes

* StatusCake sends webhook payloads as `application/x-www-form-urlencoded`, not JSON. itoc360 handles this automatically.
* If you want to monitor multiple endpoints, create a separate Uptime Test for each one and assign the same Contact Group to all of them.
* The **Enable Repeat Alert** option in the Contact Group should stay disabled to avoid duplicate incidents in ITOC360 for the same outage.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.itoc360.com/integrations/inbound-integrations/error-tracking-and-uptime/statuscake-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
