OpShift

Introduction

Next

Everything you need to wire OpShift into your stack — monitors, alerts, on-call schedules, and the SDKs that drive them.

OpShift is a unified incident management platform: uptime monitoring, webhook alerting, on-call rotations, and PTO — all integrated with Slack. These docs cover the concepts behind each module, the public REST API, and the official SDKs for Node / TypeScript and Python.

Start here

Quickstart
Send your first heartbeat in under five minutes. Covers signup, finding your secret, and a minimal SDK call.
Monitors
How heartbeats, intervals, grace periods, and flap detection work end-to-end.
Alerts & webhooks
Trigger alerts from anything that can speak HTTP. Filter rules, grouping, and reopen detection.
On-call schedules
Rotations, handoffs, escalation policies, and the PTO cross-check that keeps people on leave from getting paged.

Reference

TypeScript SDK
@opshift/sdk — zero dependency, Web Crypto signing, runs on Node, Edge, Workers, Deno, Bun.
Python SDK
opshift on PyPI — stdlib only, Python 3.9+, mirrors the TypeScript surface.
API authentication
HMAC-SHA256 webhook signatures, secret rotation, and the X-Webhook-Signature header.
Errors & rate limits
Status codes you can expect, per-monitor rate limits, and quota behaviour during outages.

How OpShift fits together

Every resource in OpShift is scoped to a team. A team has one webhook secret, any number of monitors and webhooks, an on-call schedule, notification policies, and a connected Slack workspace. The platform is built around four moving parts:

  • Monitors — passive heartbeat receivers. Your service pings on an interval; if the ping is missed, OpShift flips the monitor to down and fires an incident.
  • Webhooks — active alert endpoints. Anything that can POST JSON can raise an alert, with optional filter rules to suppress noise at the edge.
  • On-call schedules — who gets paged, when, and how. Rotations honour the PTO cross-check so engineers on leave are never the primary contact.
  • Notification policies — the per-channel, per-severity routing rules that decide whether a given alert pings Slack, calls a phone, or emails a digest.