Events API
Events API
The canonical Events API accepts one event per request. This makes success and retry behavior unambiguous and lets every accepted delivery map to one incident transition or update.
Endpoint
POST https://api.warnfire.com/v1/events
During the compatibility period, https://app.warnfire.com/v1/events and https://dev.craigsimon.guru/v1/events remain available for their respective environments.
Authentication
Send the service integration key in the integration_key field of the JSON request. Never place integration keys in query strings or URLs, where proxies, browsers, and providers commonly log them.
Event actions
WarnFire currently models these canonical actions:
trigger— open an incident or add a trigger/update delivery to the active incident with the same deduplication key.resolve— resolve the active incident identified by the same deduplication key.acknowledge— record a source-side acknowledgement on the incident timeline. It never stops paging; only a signed-in responder acknowledging does that (see the incident lifecycle).
Repeated trigger deliveries with changed visible payload values become numbered incident updates. Exact retries use client_event_id idempotency and do not double-page.
Metadata
Use the payload to provide a human-readable summary and description, severity, source, component, observed timestamp, environment, region, tags, labels, typed key/value details, and relevant links. Preserve provider timestamps in UTC with an explicit offset; WarnFire clients display them in the viewer’s local timezone.
Reference
Download the current OpenAPI document for complete request, response, field-limit, and error schemas.