> For the complete documentation index, see [llms.txt](https://docs.spike.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spike.sh/integrations-guideline/integrate-spike-with-statusgator.md).

# Integrate Spike with StatusGator

Send StatusGator alerts to Spike via webhook so an outage on a third-party status page pages your on-call and resolves when the service recovers.

[StatusGator](https://statusgator.com) watches the status pages of the third-party services you depend on (OpenAI, AWS, Stripe and so on), plus websites and hosts you add yourself. Point a StatusGator webhook at Spike and an outage at a vendor pages your on-call rotation, and the incident resolves itself when StatusGator reports the service as up again.

### Service and Integration

Make sure to add a StatusGator integration and copy the webhook URL.

{% content-ref url="/pages/-Ln3rb4wLUFeI-OAPcmq" %}
[Create integration and service on our dashboard](https://docs.spike.sh/integrations-guideline/create-integration-and-service-on-dashboard.md)
{% endcontent-ref %}

### Using Webhooks with StatusGator

**Step 1**

Log in to StatusGator, go to **Integrations → Webhooks** and choose **Add**.

**Step 2**

Paste the Spike webhook URL as the **Webhook URL**. The token in the URL is the credential, so treat the URL like a password. StatusGator also signs every request with an `X-Signature` header; Spike does not check it.

**Step 3**

In the **Event type** section, choose what is sent:

* **Status changes**: keep this on. It opens incidents, and the change back to `up` resolves them.
* **Early Warning Signals**: turn on to be paged when StatusGator sees signs of an outage before the provider confirms it.
* **User outage reports**: turn on to be paged when a report from your StatusGator status page is confirmed.

**Step 4**

Click **Save**, then send a test notification to confirm it reaches Spike. StatusGator does not document the test notification's body, so it may open an incident; resolve it by hand.

**Step 5 (optional)**

Choose which incidents StatusGator notifies about for each monitor. On the **Monitors** page, open a monitor's ⋮ menu, choose **Configure**, and set its **Notifications** tab, for example to major incidents only. **Board Settings → Monitor Notifications** changes this for every monitor on a board. A notification you turn off there never reaches Spike.

{% hint style="warning" %}
Spike reads webhook version 3.0, which new webhooks use. StatusGator says integrations created before June 2025 are likely on version 2.0; if the webhook's settings show it, select 3.0. Version 2.0 has no `type` and no `monitor`: Spike titles its events `StatusGator alert for {service_name}`, matches them by that title, and resolves the incident when `current_status` is `up`. Early warnings and outage reports are v3.0 only.
{% endhint %}

{% hint style="info" %}
StatusGator disables a webhook after five attempts that do not get a `200` back. If incidents stop arriving, check the webhook's **Logs** tab in StatusGator, then open **Integrations** to fix the URL and re-enable it.
{% endhint %}

## What Spike does with each event

The `type` field decides what Spike does.

| `type`                                                       | What happens                                                                                        |
| ------------------------------------------------------------ | --------------------------------------------------------------------------------------------------- |
| `StatusChange` with `status` `down`, `warn` or `maintenance` | Opens an incident, or joins the one already open for that monitor, and pages.                       |
| `StatusChange` with `status` `up`                            | Resolves the open incident for that monitor.                                                        |
| `StatusChange` with any other or missing `status`            | Treated as firing: opens or joins.                                                                  |
| `EarlyWarningSignal`                                         | Has no `status`. Opens, or joins, the incident for that monitor. It never resolves it.              |
| `OutageReport`                                               | A confirmed user report. Opens, or joins, the incident for that monitor. It never resolves it.      |
| No `type` (webhook version 2.0)                              | `current_status` `up` resolves the incident with the same title; any other value opens or joins it. |

`status` is compared after trimming and ignoring case. `maintenance` is treated as firing.

{% hint style="info" %}
An early warning or user outage report that StatusGator never follows with a `StatusChange` to `up` stays open until someone resolves it by hand.
{% endhint %}

## Incident identity

Spike identifies the incident by `monitor.id`, the stable id of your StatusGator monitor. The firing, the early warning, the user outage report and the recovery of one monitor are therefore one incident, and a recovery only closes the incident of the same monitor. The title is for display only.

`monitor.id` counts as an id when it is a non-empty string or a finite number, and is not an unexpanded template variable such as `$x`, `${x}`, `{{x}}` or `%x%`. Without a usable id Spike falls back to matching by title, which is why that shape gets the plain title described below.

## Incident title

With a `monitor.id`, a firing `StatusChange` is titled `{message} ({where} {level})`:

* `down`: `Elevated Error Rate on ChatGPT (OpenAI down)`
* `warn`: `Increased latency (OpenAI degraded)`
* `maintenance`: `Scheduled database upgrade (OpenAI under maintenance)`
* Missing or unknown `status`: the level is left out, `Elevated Error Rate on ChatGPT (OpenAI)`
* Empty `message`, naming up to two components whose `current_status` is not `up`: `Chat, Images down on OpenAI` or `Chat, Images +2 more down on OpenAI`; with no such components, `OpenAI is down`
* Unknown or missing `status` with an empty `message`: `Chat changed on OpenAI` (components named) or `OpenAI status changed`
* Early warning: `Service outage reported for OpenAI (early warning)`, or `Possible outage reported for OpenAI (early warning)` when `summary` is empty
* User outage report: `Service down reported by users for OpenAI`, from `summary.description`, or `Outage reported by users for OpenAI` without one
* Recovery (`status` `up`): `OpenAI is back up`, without the message
* No usable `monitor.id`: `StatusGator alert for OpenAI`, identical for firing and recovery, because Spike matches these by title
* Webhook version 2.0: `StatusGator alert for Heroku`, from `service_name`
* Nothing usable in the body: `StatusGator alert with no details`

`where` is the first non-empty of `monitor.display_name`, `monitor.name` (user outage reports), `service.name` and `monitor.host`, else `StatusGator monitor`. Titles never hold ids, URLs or timestamps. Whitespace is collapsed and titles are capped at 200 characters; to fit, the sentence is cut and the parenthesised name and level are kept whole.

## Fields

Required (v3.0): `type` and `monitor.id`. `status` is required to resolve; without it a `StatusChange` is treated as firing. `StatusChange` with `up` and nothing open is dropped; it never opens an incident.

Read when present: `message`, `summary` (early warnings), `summary.description` (user outage reports), `monitor.display_name`, `monitor.name`, `service.name`, `monitor.host`, `component_status_changes[].name` and `component_status_changes[].current_status`.

Everything else in the body is kept on the incident page.

## Example payloads

### Firing

```json
{
  "type": "StatusChange",
  "recorded_at": "2026-10-14T03:12:08Z",
  "service": {
    "id": "OUQJLhNcSb",
    "name": "OpenAI",
    "slug": "openai",
    "home_page_url": "https://openai.com",
    "status_page_url": "https://status.openai.com",
    "icon_url": "https://favicons.statusgator.com/openai.png",
    "landing_page_url": "https://statusgator.com/services/openai"
  },
  "monitor": {
    "id": "UIMPLWZg9D",
    "type": "ServiceMonitor",
    "display_name": "OpenAI",
    "icon_url": "https://favicons.statusgator.com/openai.png"
  },
  "board": {
    "id": "Pwg0NMcnNF",
    "name": "Production dependencies"
  },
  "status": "down",
  "previous_status": "up",
  "message": "Elevated Error Rate on ChatGPT",
  "details": "We are investigating elevated error rates for ChatGPT requests. Some users may see failed or slow responses.",
  "component_status_changes": [
    {
      "group_name": "APIs",
      "name": "Chat",
      "last_status": "up",
      "current_status": "down"
    }
  ]
}
```

### Recovery

```json
{
  "type": "StatusChange",
  "recorded_at": "2026-10-14T04:05:51Z",
  "service": {
    "id": "OUQJLhNcSb",
    "name": "OpenAI",
    "slug": "openai",
    "home_page_url": "https://openai.com",
    "status_page_url": "https://status.openai.com",
    "icon_url": "https://favicons.statusgator.com/openai.png",
    "landing_page_url": "https://statusgator.com/services/openai"
  },
  "monitor": {
    "id": "UIMPLWZg9D",
    "type": "ServiceMonitor",
    "display_name": "OpenAI",
    "icon_url": "https://favicons.statusgator.com/openai.png"
  },
  "board": {
    "id": "Pwg0NMcnNF",
    "name": "Production dependencies"
  },
  "status": "up",
  "previous_status": "down",
  "message": "Elevated Error Rate on ChatGPT",
  "details": "This incident has been resolved. ChatGPT error rates have returned to normal.",
  "component_status_changes": [
    {
      "group_name": "APIs",
      "name": "Chat",
      "last_status": "down",
      "current_status": "up"
    }
  ]
}
```

{% hint style="success" %}
This integration auto resolves
{% endhint %}
