Monitors and measurements
Create monitors, trigger checks, and read uptime, response-time, DNS, content, and performance history.
- GET /api/monitors
- POST /api/monitors
- GET /api/monitors/{id}/uptime
Developer documentation
Automate the monitoring work your team already does in Visual Sentinel. Create monitors, inspect incidents, retrieve website-health evidence, generate client reports, and keep customer-facing status workflows connected to the same source of truth.
Requests use organization API keys with scoped permissions. Keep keys server-side, rotate them when team access changes, and create separate keys for dashboards, scripts, and integrations.
Work with monitors, incidents, status pages, maintenance windows, reports, notification channels, and account metadata from one OpenAPI-described surface.
Pair API calls with webhooks, MCP tools, and scheduled jobs to sync monitoring evidence into ticketing systems, customer reports, and deployment pipelines.
These are the main API areas used by agencies, internal dashboards, deployment workflows, and reporting automations. The interactive reference below contains every parameter, request body, response, and required scope.
Create monitors, trigger checks, and read uptime, response-time, DNS, content, and performance history.
Capture screenshots, compare snapshots, manage baselines, and inspect monitored sub-pages.
List active work, inspect incident evidence, update incident state, and connect notification channels.
Generate client-facing reports, check generation status, and retrieve monitor report data.
Create public status pages, assign monitors, and manage verified customer-facing domains.
Register infrastructure, read current server details, and retrieve time-series health metrics.
Create an API key under Settings > API keys. Give each integration only the scopes it needs, keep the key on your server, and rotate it without disrupting your other workflows.
Manage API keyscurl https://visualsentinel.com/api/monitors \
--header "Authorization: Bearer vs_your_api_key"