Spike.sh
DashboardWebsiteHUB
Spike.sh
Spike.sh
  • Introduction
  • What is Spike.sh?
  • Incidents
    • What is an incident?
    • Incident lifecycle
    • Incident statuses
    • How to change incident status?
    • Acknowledge timeout
    • Grouping incidents
    • Priority and Severity
    • Mute alerts
    • Reassign incidents
    • Sharing incidents
    • Why does message parsing fail?
    • Rate limiting on duplicate incidents
  • Alerts
    • Phone
    • SMS
    • Mobile app alerts
    • E-mail
    • Slack
    • Microsoft Teams
    • WhatsApp
    • Telegram
    • Pushover
    • Discord
    • Alert rules
    • Title Remapper
    • Personal alerts management
      • During office hours
      • Out of office
      • Resolved incident alerts
      • Deep work & Cooldown modes
  • Services
    • Introduction to services on Spike
  • Escalations
    • Introduction to escalations
    • How to create an escalation policy?
    • Repeat escalations
    • Archive escalation policy
  • Collaboration
    • Task management integrations
      • JIRA Cloud
      • JIRA server (self-hosted)
      • ClickUp
      • Linear
      • Shortcut
    • Helpdesk integrations
      • Zendesk
      • Freshdesk
      • Supportpal
    • War rooms
  • On-call schedules
    • Introduction to On-call schedules
    • Create On-call schedule
    • Introduction to Slots in schedules
    • Introduction to Layers in on-call schedules
    • Override an on-call
    • Add on-call schedule to your calendar
    • Notifications for on-call shifts
    • Change on-call rotation day
  • Playbooks
    • Introduction to Playbooks
    • Actions in Playbooks
    • Automating your Playbooks
    • Run Playbooks manually
  • Status Pages
    • Create Status page
    • Style your status page
    • Incidents on status page
    • Create Planned Maintenance on status page
    • Edit Planned Maintenance
    • Add custom domain to status page
    • Manage your subscribers
    • Embed status page notifications on your website
    • Live status widget
  • Uptime
    • Create Uptime monitor
    • Link uptime to Status Page
  • Integrations guidelines
    • Create integration and service on our dashboard
    • Setup integrations
    • Archive an integration
    • Integrating with Webhooks
    • Integrate Spike with Email
    • Integrate Spike with AWS
    • Integrate Spike with Google Cloud
    • Integrate Spike with Sematext
    • Integrate Spike with Healthchecks
    • Integrate Spike with Pingdom
    • Integrate Spike.sh with Sentry
    • Integrate Spike with Apex ping
    • Integrate Spike with Uptime Robot
    • Integrate Spike with Twilio
    • Integrate Spike with Microsoft Azure
    • Integrate Spike with Honeybadger
    • Integrate Spike with Rollbar
    • Integrate Spike with Travis CI
    • Integrate Spike with Heroku
    • Integrate Spike with Datadog
    • Integrate Spike with Axiom
    • Integrate Spike with Needle.sh
    • Integrate Spike with Cronitor
    • Integrate Spike with Bugsnag
    • Integrate Spike with Grafana
    • Integrate Spike with Prometheus
    • Integrate Spike with Instana
    • Integrate Spike with Zapier
    • Integrate Spike with Librato
    • Integrate Spike with Checkly
    • Integrate Spike with AppSignal
    • Integrate Spike with New Relic
    • Integrate Spike with Site24x7
    • Integrate Spike with Stackify
    • Integrate Spike with Scout-apm
    • Integrate Spike with Oh-Dear
    • Integrate Spike with Nixstats
    • Integrate Spike with Server Density
    • Integrate Spike with Raygun
    • Integrate Spike with Lightstep
    • Integrate Spike with Runscope
    • Integrate Spike with Honeycomb
    • Integrate Spike with Graylog
    • Integrate Spike with Checkmk
    • Integrate Spike with Hyperping
    • Integrate Spike with Epsagon
    • Integrate Spike with Uptime
    • Integrate Spike with Splunk
    • Integrate Spike with Sumo Logic
    • Integrate Spike with Thousand Eyes
    • Integrate Spike with Loggly
    • Integrate Spike with Elastic Cloud
    • Integrate Spike with App Optics
    • Integrate Spike with NodePing
    • Integrate Spike with Scalyr
    • Integrate Spike with Moogsoft
    • Integrate Spike with AppDynamics
    • Integrate Spike with Dynatrace
    • Integrate Spike with CopperEgg
    • Integrate Spike with Coralogix
    • Integrate Spike with ElastAlert
    • Integrate Spike with LogDNA
    • Integrate Spike with Zebrium
    • Integrate Spike with LibreNMS
    • Integrate Spike with Uptime Kuma
    • Integrate Spike with Logentries
    • Integrate Spike with Logz
    • Integrate Spike with Ghost Inspector
    • Integrate Spike with Hetrix Tools
    • Integrate Spike with LogRocket
    • Integrate Spike with StatusCake
    • Integrate Spike with Sysdig
    • Integrate Spike with Wavefront
    • Integrate Spike with Buildkite
    • Integrate Spike with Semaphore
    • Integrate Spike with Better Uptime
    • Integrate Spike with Hexowatch
    • Integrate Spike with PM2
    • Integrate Spike with Cloudflare
    • Integrate Spike with Zabbix
    • Integrate Spike with Tenderly
    • Integrate Spike with Xitoring
    • Integrate Spike with Crowdstrike
    • Integrate Spike with GitHub Workflows
    • Integrate Spike with Solarwinds Orion
    • Integrate Spike with Airbrake.io
    • Updown.io
  • Administration
    • Roles and access
    • SSO
    • Enforce login
    • Our notification numbers
    • Contact the support team
    • Adding team members
    • Check if team is getting alerts
    • Removing team members
  • Additional resources
    • Create a badge
Powered by GitBook
On this page
  • Create an incident using our webhooks integration
  • Create an incident
  • When is a new incident NOT created?
  • What is the title's significance?
  • What happens if I miss adding a title?
  • Auto-resolve incident

Was this helpful?

Edit on GitHub
  1. Integrations guidelines

Integrating with Webhooks

Use spike's webhook and create an incident from your code.

PreviousArchive an integrationNextIntegrate Spike with Email

Last updated 2 years ago

Was this helpful?

Create an incident using our webhooks integration

Each webhook is unique to the service and escalation policy. Make sure you create a webhook integration and copy the webhook URL. .

From your code, you can create an incident simply by making a POST request.

Create an incident

POST https://hooks.spike.sh/:token/push-events

Path Parameters

Name
Type
Description

token

string

Unique token for your webhook integration

Request Body

Name
Type
Description

title

string

This will be the title of your incident. Failing to add this will create an empty incident. Read more about this below 👇

body

string

Accepts objects and strings. This data will be in your incident details

severity

string

Sets the severity on your incident. Options are

sev1, sev2, and sev3.

priority

string

Sets the priority on your incident. Options are

p1, p2, p3, p4, and p5

{ Ok: true }
{}

The above request will create a new incident. Please make sure you have used the correct webhook URL. If you have copied the URL from the dashboard then the token **** should already be present. A new incident is created soon as make a POST request. A successful request will get you 200 HTTP response status code.

When is a new incident NOT created?

If the integration has an open incident (not resolved state) __ with the same title then a new incident will NOT be created.

What is the title's significance?

The title plays an important role really. A new incident will use this title and it will be sent on all alter channels. The title acts as a unique identifier to perform group actions, suppress repeated incidents and also to auto-resolve them.

What happens if I miss adding a title?

Failing to add title would create incidents with no message. This also means that it will NOT group, suppress or auto-resolve these incidents.

We highly recommend you add a title to your POST request while creating an incident

Auto-resolve incident

POST https://hooks.spike.sh/:token/push-events

Path Parameters

Name
Type
Description

token

string

Unique token for your webhook integration

Request Body

Name
Type
Description

status

string

resolve

body

string

As of now, you can add any message about the incident you would like here. Accepts objects too.

title

string

This will be the title of your incident. Failing to add this will create an empty incident title with all other parameters. Read more about this below 👇

{ Ok: true }
{}

The above request will automatically resolve incidents. We use the title and the token to uniquely get open incidents and resolve them.

All you need is to add the status parameter as 'resolve' in your POST request. The rest of the parameters are the same as creating incident request.

Make sure to have the same title while resolving, otherwise it won't work.

Know how