Skip to content
Spike logo

Connectors / IT · HTTP Connector

Automate Spike with Tray.ai

Create an incident, create an on-call schedule and create an escalation policy in Spike. Connect Spike to the rest of your IT stack with Tray.ai.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.

See all connectors

What can you do with Spike on Tray.ai?

Spike is an incident management platform for on-call teams, covering alerts, on-call schedules, escalation policies and public status pages. Tray.ai connects to Spike through the HTTP Connector, so your workflows can call the Spike API alongside the rest of your stack.

  • Create an incident in Spike when your monitoring tool reports a failed health check.
  • Get the active shift and post who is on call to the engineering team chat each morning.
  • Resolve an incident in Spike when the linked ticket is closed in your issue tracker.
  • Create a status page incident so customers see an outage reported by your support team.
Connects through
HTTP Connector
Authentication
An API key in a request header
Base URL
https://api.spike.sh

Set it up

Connect Spike to Tray.ai

Each step uses Spike's own API details, from its documentation.

Step 1

Save Spike's API key

Save the key as a Tray.ai authentication. The HTTP Client puts it in the request header, read from $.auth. The key stays out of the workflow and out of the logs.

Step 2

Point the HTTP Client at the API

Add an HTTP Client step and use https://api.spike.sh as the base URL. Or paste a cURL example from Spike's API docs, and Tray.ai fills in the method, URL, and headers.

Step 3

Start with “List incidents”

It's one of 27 documented actions, under Incidents. The response comes back as data the next step can map into your other apps.

Step 4

Hand it to an AI agent

Wrap “Get an incident” and “Create an incident” in workflows, and Tray.ai's Agent Gateway for MCP publishes them as governed tools Claude and other AI agents can call.

What the Spike API covers

6 resources and 27 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Connecting it takes a few clicks: here's how.

Incidents

  • List incidents
  • Get an incident
  • Create an incident
  • Add a responder
  • Remove a responder
  • Get incident activity log

Incident actions

  • Acknowledge an incident
  • Resolve an incident
  • Escalate an incident
  • Set incident priority
  • Set incident severity

On-call schedules

  • List on-call schedules
  • Create an on-call schedule
  • Edit an on-call schedule
  • Get the active shift

Escalation policies

  • List escalation policies
  • Create an escalation policy
  • Update an escalation policy
  • Archive an escalation policy

Services

  • List services
  • Create a service
  • Update a service
  • List incidents for a service

Status page incidents

  • List status page incidents
  • Create a status page incident
  • Edit a status page incident
  • Add a status update

Checked against Spike's own documentation on 2026-10-22

docs.spike.sh/spike-api-docs/getting-started

Frequently asked questions

What can a Tray.ai workflow do in Spike?

+

The Spike API documents 27 actions across 6 resources (Incidents, Incident actions, On-call schedules, Escalation policies, Services, Status page incidents). For example: List incidents; Acknowledge an incident; List on-call schedules. A workflow can make any documented call through the HTTP Connector.

How does Tray.ai authenticate with Spike?

+

The Spike API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

See Spike working against your stack.

We'll walk through a tailored demo with your systems plugged in.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.