How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Spike.sh Incidents API

Incident management endpoints

Spike.sh Incidents API is one of 17 APIs that Spike.sh publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Incidents. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 12 operations across 12 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.spike.sh, https://statuspage.spike.sh.

12 operations 12 paths 2 schemas 11 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.spike.sh
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Spike.sh Incidents API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — API key generated from https://app.spike.sh/api

Paths & Operations 12

Across 12 paths, the API surfaces 12 operations — 11 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Incidents 12

Incident management endpoints

GET
/incidents
Fetch incidents
getIncidents 1 param → 200401
GET
/incidents/all-occurrences
Get all incident occurrences
getAllIncidentOccurrences 8 params → 200401
POST
/incidents/create
Create incident
createIncident 1 param body → 200400401
GET
/incidents/{counterId}
Fetch incident info
getIncident 2 params → 200401404
GET
/incidents/{counterId}/get-previous-incidents
Fetch previous occurrences
getIncidentPreviousOccurrences 2 params → 200401404
GET
/incidents/{counterId}/previous-incident/{_id}
Fetch single previous occurrence
getIncidentSinglePreviousOccurrence 3 params → 200401404
GET
/incidents/{counterId}/incident-context
Fetch incident context
getIncidentContext 2 params → 200401404
GET
/incidents/{counter_id}/activity-log
Fetch activity log
getIncidentActivityLog 2 params → 200401404
GET
/incidents/acknowledged
Fetch acknowledged incidents
getAcknowledgedIncidents 1 param → 200401
GET
/incidents/triggered
Fetch triggered incidents
getTriggeredIncidents 1 param → 200401
GET
/incidents/assigned-to-user
Fetch user-assigned incidents
getIncidentsAssignedToUser 2 params → 200401
GET
/incidents/overview
Fetch incident overview
getIncidentOverview 2 params → 200401

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Incident (11 properties), Error (2 properties). Each schema is shown below with its type and property counts.

Error
object
2 properties
Incident
object
11 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

spike-sh-incidents-api-openapi.yml Raw ↑

Other APIs Spike.sh publishes across the network.

Spike.sh Alert Rules API
Spike.sh Components API
Spike.sh Escalations API
Spike.sh Incident Actions API
Spike.sh Integrations API
Spike.sh On-Call Overrides API
Spike.sh On-Call Schedules API
Spike.sh Orgs API
Spike.sh Planned Maintenances API
Spike.sh Services API
Spike.sh Status Page Incidents API
Spike.sh Status Pages API
Where this information came from

This is an independent, third-party profile of Spike.sh Incidents API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.