Overview
Pause a monitor to temporarily stop all monitoring checks. Paused monitors do not trigger alerts or record check results but retain all configuration. Resume the monitor at any time to restart checks.Authentication
All requests must include authentication via:- API Key:
X-API-Key: YOUR_API_KEY
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Monitor UUID (e.g., mon_1234567890abcdef) |
Request Example
Request Details
| Aspect | Value |
|---|---|
| Content-Type | Not required (no body) |
| Body | Empty |
| Query Parameters | None |
Response
Success Response (200 OK)
Pause Effects
When a monitor is paused:- Check Scheduling: No new checks are scheduled
- Existing Checks: In-flight checks complete but results are not recorded
- Notifications: No alerts or notifications are sent
- Data Recording: No new check results added to historical data
- Configuration: All settings remain unchanged
- Status: Monitor appears as
pausedin queries - Plan Limits: Monitor still counts towards active monitor limit
When to Pause
Consider pausing monitors for:- Maintenance: During scheduled system maintenance windows
- Testing: When testing application changes
- Temporary Issues: When addressing known problems
- Cost Control: To pause monitoring without deleting configuration
- Deployment: During application deployments
Pausing vs. Deleting
| Aspect | Pause | Delete |
|---|---|---|
| Configuration Retained | Yes | Yes |
| Counts Toward Limit | Yes | No |
| Can Resume | Yes | No (soft-deleted) |
| Visible in Lists | No | No |
| Historical Data | Accessible | Archived |
| Notifications Sent | No | No |
Error Codes
| Code | Status | Description |
|---|---|---|
INVALID_MONITOR_ID | 400 | Missing or invalid monitor ID |
AUTHENTICATION_REQUIRED | 401 | Missing or invalid authentication |
MONITOR_NOT_FOUND | 404 | Monitor not found or access denied |
MONITOR_PAUSE_FAILED | 500 | Unexpected pause failure |