Firehydrant

FireHydrant provides end-to-end incident lifecycle management: declaration, automated runbook execution (create Slack channel, page on-call, update status page), role assignment, timeline tracking, and retrospective templating. Signals (inbound alert integration) replace manual escalation for automated incident creation from monitoring tools. Its REST API enables programmatic incident operations for agents: create/update/resolve incidents, trigger runbooks, manage services and environments, and pull retrospective data for analysis. Larger enterprise footprint than some competitors; strong on reliability operations tooling. Confidence is docs-derived.

REST API at api.firehydrant.io/v1. Resources: incidents, incident_events, runbooks, services, environments, severities, teams, on_call_schedules, signals. POST /v1/incidents creates an incident (name, severity, services affected). GET /v1/incidents lists with filtering. PATCH /v1/incidents/{id} updates milestone (started, detected, acknowledged, mitigated, resolved, postmortem_started). POST /v1/incidents/{id}/attachments attaches notes/links. Runbooks: GET /v1/runbooks lists available runbooks. Signals: POST /v1/signals/ingest ingests alert payloads from monitoring tools.

OAuth2 access tokens or API key as Bearer token via Authorization: Bearer header. API keys created in FireHydrant Organization → API Tokens. Org-scoped access; no per-resource permissions. OAuth2 app registration available for partner integrations. HTTPS enforced. Token rotation via dashboard. FireHydrant also uses session auth for browser flows; REST access uses API tokens exclusively.

Standard HTTP status codes with JSON error bodies (errors array with messages). 401 for invalid token, 404 for missing resource, 422 for invalid state transitions (e.g., resolving an incident that is still active). Rate limits documented per plan tier. Webhook event delivery for incident lifecycle changes configurable in Settings. FireHydrant SaaS uptime at status.firehydrant.io. Retry guidance available in rate-limit responses.

developers.firehydrant.io provides complete API reference, authentication documentation, webhook guide, and integration reference for monitoring/alerting tools. Getting started requires a FireHydrant account (trial available). Documentation quality is solid; API reference covers all endpoints with request/response schemas. SDKs not officially maintained; community-maintained Go and Ruby clients exist. Support via help.firehydrant.io.