Full reference for the Rumbliq REST API, integration guides, and developer documentation. Use the API to create monitors, fetch check history, manage credentials, configure alerts, and integrate Rumbliq into your CI/CD pipeline.
Already have an account? Generate an API key. New to Rumbliq? Read the getting started guide.
All API requests require Authorization: Bearer dk_live_.... Generate keys in the dashboard. Keys are scoped to a single user and inherit that user's plan limits.
POST /v1/monitors creates a monitor. GET /v1/monitors lists them. Supported types: http (schema drift + uptime), heartbeat, dns, domain, ssl, ping, port, deprecation, sequence, webhook.
GET /v1/monitors/{id}/checks returns historical check results with response body diffs, schema diffs, and status codes.
GET /v1/monitors/{id}/baseline shows the current schema baseline. POST /v1/monitors/{id}/baseline/reset re-baselines from the latest check.
POST /v1/alerts creates alert destinations: webhook, Slack, Discord, PagerDuty, OpsGenie, email, SMS, or voice call.
POST /v1/credentials stores encrypted API credentials (bearer tokens, API keys, basic auth, OAuth2 client credentials) for use with monitors that require authentication. AES-256-GCM encrypted, per-user keys. Pro plan and above.
POST /v1/sequences creates a multi-step API workflow. Chain HTTP requests, extract response values, and use them in subsequent steps with assertions on status, body, and schema.
The full machine-readable specification is at /v1/openapi.json. This page renders it interactively with try-it-out support for every endpoint.
Subscribe to events via webhook endpoints in the dashboard. Events include schema drift detection, alert state changes, monitor down/up transitions, and incident lifecycle changes. Signed with HMAC-SHA256 for verification.
100 requests per minute per user. Higher limits available on Business and Enterprise. Burst capacity allowed for bulk monitor creation.
All responses use the envelope { "data": T | null, "error": { "code": string, "message": string } | null }. HTTP status reflects the outcome; check error.code for machine-readable error identifiers.