API & Webhooks That Integrate Seamlessly

Our REST API provides full programmatic access to all monitoring features. You can create, update, and delete monitors, retrieve real-time status and historical data, configure alerts and webhooks, export logs and analytics, and manage your entire monitoring setup programmatically.

We use HMAC-based authentication for security. Include your API key in the X-Api-Key header and sign requests with your secret key. This ensures your API calls are secure and can't be intercepted or tampered with.

The API allows you to retrieve data and manage your monitoring setup programmatically. Webhooks send real-time notifications to your systems when monitoring events occur (like downtime or recovery). Both use the same authentication system for security.

Webhook payloads include an HMAC signature in the X-Exit1-Signature header. You can verify this signature using your webhook secret to ensure the notification is genuinely from exit1.dev and hasn't been tampered with during transmission.

Webhook payloads include comprehensive information about the monitoring event: website details, status codes, response times, error messages, timestamp, and event type. This gives you all the context needed to handle the alert appropriately.

While the core webhook structure is standardized for consistency, you can add custom headers to webhooks for authentication or routing purposes. The payload includes all relevant monitoring data to help you build robust integrations.

We provide generous rate limits to accommodate most use cases: 1000 requests/hour for general API calls, 2000 requests/hour for analytics data, and 500 requests/hour for alerting operations. These limits are designed to prevent abuse while allowing legitimate usage.

Yes, we provide comprehensive OpenAPI documentation with examples, authentication details, and endpoint descriptions. The documentation is interactive and allows you to test API calls directly from the browser to understand how everything works. Visit docs.exit1.dev/api-reference for the full API reference.