Skip to main content

​
Overview

Resume a paused monitor to restart monitoring checks. The monitor immediately returns to its active state and resumes the normal check schedule. All configuration remains unchanged from when it was paused.

​
Authentication

All requests must include authentication via:
  • API Key: X-API-Key: YOUR_API_KEY

​
Path Parameters

ParameterTypeRequiredDescription
idstringYesMonitor UUID (e.g., mon_1234567890abcdef)

​
Request Example

POST /api/monitors/mon_1234567890abcdef/resume
No request body is required.

​
Request Details

AspectValue
Content-TypeNot required (no body)
BodyEmpty
Query ParametersNone

​
Response

​
Success Response (200 OK)

{
  "success": true,
  "data": {
    "id": "mon_1234567890abcdef",
    "organization_id": "org_1234567890abcdef",
    "project_id": "proj_1234567890abcdef",
    "name": "Production API Health",
    "type": "HTTP",
    "target": "https://api.example.com/health",
    "interval_seconds": 60,
    "timeout_ms": 10000,
    "status": "active",
    "monitoring_regions": ["asia", "europe"],
    "tags": ["production", "critical"],
    "http_config": {
      "method": "GET",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      },
      "follow_redirects": true,
      "max_redirects": 5,
      "expected_status_codes": [200, 201]
    },
    "notification_profile_ids": ["uuid-1", "uuid-2"],
    "created_at": "2024-12-26T10:30:00Z",
    "updated_at": "2024-12-26T16:00:45Z",
    "created_by": "user_1234567890abcdef",
    "is_deleted": false,
    "is_active": true
  }
}

​
Resume Behavior

When a monitor is resumed:
  1. Immediate Activation: Monitor status changes to active
  2. Check Scheduling: New checks are immediately scheduled
  3. Next Check: First check scheduled for next interval occurrence
  4. Notifications: Alerts resume based on new check results
  5. Configuration: All previous settings are maintained
  6. Historical Data: Gap in data reflects pause period
  7. Uptime Calculation: Paused period may affect uptime percentage

​
Plan Limit Enforcement

Resuming a monitor may be blocked if:
  1. Active Monitor Limit: Organization has reached max active monitors
  2. Paused Monitor Counts: Paused monitors still count toward limit
Error Response (403 Forbidden): 
{
  "success": false,
  "error": {
    "code": "MONITOR_LIMIT_REACHED",
    "message": "Active monitor limit reached (50). Upgrade your plan to resume more monitors."
  }
}

​
Resuming After Maintenance

Resume immediately triggers a check: 
# At 16:00:45 - Resume monitor
POST /api/monitors/mon_1234567890abcdef/resume

# Monitor scheduled to check again immediately (within 1-2 seconds)
# Then continues on its regular interval (60s for this example)
# Next checks: 16:01:45, 16:02:45, 16:03:45, etc.

​
Data Gap During Pause

When a monitor is paused and then resumed:
  • Check results dataset shows a gap
  • Uptime percentage calculation:
    • Option 1: Treats pause period as uptime (historical behavior)
    • Option 2: Excludes pause period from calculation
    • Check your account settings for configured behavior
Example with 1-hour pause:
  • Before pause: 30 successful checks
  • Pause: 1 hour (10 expected checks skipped)
  • After resume: 30 successful checks
  • Total uptime: (30 + 30) / (30 + 10 + 30) or (30 + 30) / (30 + 30) depending on config

​
Error Codes

CodeStatusDescription
INVALID_MONITOR_ID400Missing or invalid monitor ID
AUTHENTICATION_REQUIRED401Missing or invalid authentication
MONITOR_NOT_FOUND404Monitor not found or already deleted
MONITOR_LIMIT_REACHED403Active monitor limit exceeded on plan
MONITOR_RESUME_FAILED500Unexpected resume failure

​
Examples

# Resume a monitor
curl -X POST https://api.uptimeio.com/api/monitors/mon_1234567890abcdef/resume \
  -H "X-API-Key: YOUR_API_KEY"