Suppressed Incidents

Read incident occurrences that were suppressed by de-duplication or alert rules.

Fetch suppressed incidents

get

Fetches suppressed incidents for an incident.

Authorizations

x-api-keystringRequired

Your organisation's API key. Create one in the Spike dashboard under Settings > API. Sent on every request as the x-api-key header.

x-team-idstringRequired

The target team's _id — a 24-character hex ObjectId such as 5f2b1c4d9e8a7b6c5d4e3f21. This is NOT the short uid slug (e.g. eng) shown in dashboard URLs; passing the uid will not resolve a team. Read the _id from GET /teams/get-all-teams or GET /teams/get-my-teams.

REQUIRED for: GET /on-calls (API-key callers get 400 without it), POST /on-calls, and every team-scoped read that declares it — the /incidents/* and /services/* listings, /escalations, /automation/rules and the integration endpoints.

OPTIONAL for: the incident action endpoints (acknowledge, resolve, escalate, unacknowledge), which derive the organisation from the API key itself; PUT /on-calls/{oncallId} and the on-call layer endpoints, which fall back to the organisation's default team; and org-wide reads such as GET /orgs/info and GET /users, which ignore it.

When supplied it must name a team inside the API key's organisation. A team from another organisation is rejected with 403.

Path parameters

counterIdstringRequired

counterId parameter

Header parameters

x-api-keystringRequired

Your API key. Find it in your Spike dashboard under Settings > API.

x-team-idstringRequired

The team's _id — a 24-character hex ObjectId, NOT the short uid slug. Read it from GET /teams/get-all-teams.

Example: 5f2b1c4d9e8a7b6c5d4e3f21

Responses

200

Successful response

application/json

incidentEventsobject[]Optional

currentPagenumberOptional

perPagenumberOptional

totalnumberOptional

401

Unauthorized

application/json

404

Not found

application/json

get/incidents/{counterId}/suppressed-incidents

GET /incidents/{counterId}/suppressed-incidents HTTP/1.1
Host: api.spike.sh
x-api-key: text
x-team-id: text
Accept: */*

{
  "incident": {
    "_id": "65a1f4c8e9b2d3a4f5c6b7a8",
    "counterId": "eng-116",
    "message": "High CPU on api-prod-3",
    "status": "NACK",
    "priority": "p1",
    "severity": "sev1",
    "counter": 116,
    "org": "5f72e289b17d1656e0115098",
    "teams": [
      "5f2b1c4d9e8a7b6c5d4e3f21"
    ],
    "integration": {
      "_id": "62a1b2c3d4e5f60718293a4b",
      "name": "AWS CloudWatch",
      "token": "a1b2c3d4e5f6a7b8c9d0"
    },
    "service": {
      "_id": "61d2c3b4a5968778695a4b3c",
      "name": "API",
      "counterId": 4
    },
    "escalation": {
      "_id": "63c9a1b2d4e5f60718293a4b",
      "name": "Engineering primary"
    },
    "responders": [],
    "createdAt": "2026-03-13T09:41:00.000Z",
    "NACK_at": "2026-03-13T09:41:00.000Z"
  },
  "incidentEvents": [
    {
      "_id": "65a1f4c8e9b2d3a4f5c6b901",
      "createdAt": "2026-03-13T09:41:00.000Z",
      "message": "High CPU on api-prod-3"
    }
  ],
  "currentPage": 1,
  "perPage": 20,
  "total": 1
}

Fetch a suppressed incident

get

Fetches a suppressed incident with it's details for an incident. A suppressed incident is an incident that is created when an incident is in triggered state and a new incident is created for the same service.

Authorizations

x-api-keystringRequired

Your organisation's API key. Create one in the Spike dashboard under Settings > API. Sent on every request as the x-api-key header.

x-team-idstringRequired

The target team's _id — a 24-character hex ObjectId such as 5f2b1c4d9e8a7b6c5d4e3f21. This is NOT the short uid slug (e.g. eng) shown in dashboard URLs; passing the uid will not resolve a team. Read the _id from GET /teams/get-all-teams or GET /teams/get-my-teams.

REQUIRED for: GET /on-calls (API-key callers get 400 without it), POST /on-calls, and every team-scoped read that declares it — the /incidents/* and /services/* listings, /escalations, /automation/rules and the integration endpoints.

OPTIONAL for: the incident action endpoints (acknowledge, resolve, escalate, unacknowledge), which derive the organisation from the API key itself; PUT /on-calls/{oncallId} and the on-call layer endpoints, which fall back to the organisation's default team; and org-wide reads such as GET /orgs/info and GET /users, which ignore it.

When supplied it must name a team inside the API key's organisation. A team from another organisation is rejected with 403.

Path parameters

counterIdstringRequired

counterId parameter

_idstringRequired

_id parameter

Header parameters

x-api-keystringRequired

Your API key. Find it in your Spike dashboard under Settings > API.

x-team-idstringRequired

The team's _id — a 24-character hex ObjectId, NOT the short uid slug. Read it from GET /teams/get-all-teams.

Example: 5f2b1c4d9e8a7b6c5d4e3f21

Responses

200

Successful response

application/json

incidentEventobjectOptional

401

Unauthorized

application/json

404

Not found

application/json

get/incidents/{counterId}/suppressed-incidents/{_id}

GET /incidents/{counterId}/suppressed-incidents/{_id} HTTP/1.1
Host: api.spike.sh
x-api-key: text
x-team-id: text
Accept: */*

{
  "incidentEvent": {
    "_id": "65a1f4c8e9b2d3a4f5c6b901",
    "createdAt": "2026-03-13T09:41:00.000Z",
    "message": "High CPU on api-prod-3",
    "metadata": {
      "instanceId": "i-0abc123"
    }
  },
  "incident": {
    "_id": "65a1f4c8e9b2d3a4f5c6b7a8",
    "counterId": "eng-116",
    "message": "High CPU on api-prod-3",
    "status": "NACK",
    "priority": "p1",
    "severity": "sev1",
    "counter": 116,
    "org": "5f72e289b17d1656e0115098",
    "teams": [
      "5f2b1c4d9e8a7b6c5d4e3f21"
    ],
    "integration": {
      "_id": "62a1b2c3d4e5f60718293a4b",
      "name": "AWS CloudWatch",
      "token": "a1b2c3d4e5f6a7b8c9d0"
    },
    "service": {
      "_id": "61d2c3b4a5968778695a4b3c",
      "name": "API",
      "counterId": 4
    },
    "escalation": {
      "_id": "63c9a1b2d4e5f60718293a4b",
      "name": "Engineering primary"
    },
    "responders": [],
    "createdAt": "2026-03-13T09:41:00.000Z",
    "NACK_at": "2026-03-13T09:41:00.000Z"
  }
}