Developer documentation

Everything developers need to integrate Stitch.

Use this hub to connect alerting, chat, deployments, customer data, webhooks, and internal tools to Stitch reliability workflows.

Start quickstart View integrations

POST /v1/incidents

{
  "source": "datadog",
  "severity": "sev2",
  "service": "payments-api",
  "summary": "Card auth failures above baseline",
  "customer_impact": true
}

Quickstart

Ship your first integration in four steps.

Start with a webhook or API key, then layer in routing, ownership, and customer impact once events are flowing.

Get implementation help

Create credentials

Generate an API key per environment, restrict scopes, and store secrets in your preferred vault.

Send a test event

Post a sample alert or deployment event and confirm it appears in the Stitch event stream.

Map services and owners

Attach events to services, escalation policies, teams, regions, and customer-impact rules.

Automate response

Create channels, assign responders, draft updates, and trigger runbooks from trusted events.

Integration catalog

Connect the systems that define incident context.

Each integration should answer one operational question: what changed, who owns it, who is affected, or what needs to happen next.

Build a custom integration

Alerts and monitoring

Connect alert sources, normalize severity, route ownership, and attach monitor context to incidents.

Datadog Grafana Prometheus New Relic

Chat and collaboration

Create incident channels, sync timelines, assign actions, and keep responders updated where they work.

Slack Microsoft Teams Webhooks Email

Deployments and code

Link deploys, pull requests, commits, feature flags, and recent changes to every investigation.

GitHub GitLab CI/CD LaunchDarkly

Customer operations

Map affected customers, support tickets, status updates, and account impact into response workflows.

Zendesk Intercom HubSpot Status pages

API and webhooks

Use predictable contracts for custom workflows.

When a native connector is not available, use incoming webhooks and API endpoints to create incidents, append timeline events, update impact, or close the loop after remediation.

Idempotency keys for retry-safe event delivery
HMAC signatures for webhook verification
Sandbox events for local and staging validation

Example webhook handler

app.post("/stitch/webhooks", verifySignature, async (req, res) => {
  const event = req.body;

  await stitch.timeline.create({
    incidentId: event.incident_id,
    type: "deployment",
    title: event.title,
    url: event.url
  });

  res.status(202).send({ received: true });
});

Operational guidance

Integration matters developers usually ask about.

Use environment-specific API keys, rotate them regularly, and limit each integration to the smallest required scope.

Use exponential backoff, idempotency keys, and dead-letter queues so duplicate events do not create duplicate incidents.

Send enough context for responders to act: service, environment, severity, summary, links, runbook, owner, deployment reference, and customer impact.

Yes. Share your source system, event shape, security constraints, and desired workflow, and the Stitch team can help design the connector.

Need integration help?

Bring your incident stack into one workflow.

Tell us which systems you need to connect and what response workflow you want Stitch to automate.

Talk to an integration engineer