API Monitoring Quick Setup Guide
This guide walks you through creating your first API monitoring check in UptimeDock. You'll learn how to configure HTTP requests, add custom headers, send POST data, and validate response content.
Prerequisites
Before you begin, make sure you have:
- An active UptimeDock account
- The API endpoint URL you want to monitor
- Any required authentication tokens or API keys
- Sample request payload (if monitoring POST/PUT endpoints)
Step 1: Select Check Type
Navigate to the Create New Check page. From the check type selection screen, find the Website Monitoring category and click Continue on the API card.
API monitoring is designed for REST endpoints and includes advanced features like custom HTTP methods, request headers, and response body validation. Choose Website monitoring for simple webpage availability checks.
Step 2: Basic Configuration
Configure the basic settings for your API monitoring check:
| Field | Description | Example |
|---|---|---|
| Tag | A friendly name to identify this check | Payment API - Health Check |
| API Endpoint | The full URL of your API endpoint | https://api.example.com/v1/health |
| HTTP Method | The HTTP method to use for requests | GET, POST, PUT, DELETE, PATCH, HEAD |
| Frequency | How often to check your API | Every 30 seconds |
Select the appropriate HTTP method based on your API endpoint:
| Method | Use Case |
|---|---|
GET | Health check endpoints, status APIs, data retrieval |
POST | Authentication endpoints, data submission, webhooks |
PUT | Update operations, configuration endpoints |
DELETE | Cleanup endpoints (use with caution) |
PATCH | Partial updates |
HEAD | Lightweight checks, header-only validation |
Step 3: Choose Monitor Regions
Select the geographic regions from which UptimeDock will monitor your API:
| Region | Locations |
|---|---|
| Europe | London, Milan, Paris, Stockholm, Dublin, Frankfurt |
| United States | California, Ohio, Oregon, Virginia |
You can select individual locations, entire regions, or click Select all regions for comprehensive global coverage. Monitoring from multiple regions helps detect regional issues and provides a better picture of global API performance.
Step 4: Verification Options
Configure verification settings to reduce false positives:
| Option | Description | Recommended |
|---|---|---|
| Enable simultaneous monitoring | All selected regions check at the same time | Disable for most cases |
| Verify down from another agent | A second agent confirms outages before alerting | ✅ Enable |
We strongly recommend enabling Verify down from another agentfor production APIs. This prevents false alerts caused by temporary network issues between monitoring agents and your API servers.
Step 5: Configure Post Data
If your API endpoint requires a request body (for POST, PUT, or PATCH methods), expand the Post Data section.
First, select the content type from the dropdown:
| Content Type | Use Case |
|---|---|
| None | No request body (default for GET, HEAD) |
| JSON | Most REST APIs (application/json) |
| XML | SOAP or XML-based APIs (application/xml) |
| Text | Plain text payloads (text/plain) |
| JavaScript | JavaScript payloads (application/javascript) |
| HTML | HTML content (text/html) |
After selecting a content type, enter your request body in the text area. For example, a JSON login request:
{
"email": "monitor@example.com",
"password": "your-secure-password"
}Avoid using production credentials in API monitoring requests. Create dedicated monitoring-only API keys or test accounts with limited permissions.
Step 6: Add Request Headers
Many APIs require authentication or custom headers. Click New in the Request Headers section to add headers:
| Header Name | Example Value | Use Case |
|---|---|---|
Authorization | Bearer eyJhbGciOiJI... | JWT or OAuth token authentication |
X-API-Key | your-api-key-here | API key authentication |
Accept | application/json | Expected response format |
X-Custom-Header | custom-value | Any custom header your API requires |
You can add multiple headers. Each header requires both a name and value. To remove a header, click the delete button next to it.
When you select a content type in the Post Data section, the Content-Typeheader is automatically added. You don't need to add it manually.
Step 7: Response Body Validation
Response body validation allows you to verify that your API returns expected content. This catches issues where an API returns HTTP 200 but with error content.
Toggle on Response Body Validation and configure:
| Validation Type | Description | Example |
|---|---|---|
| Contains | Response must include the specified text | "status":"success" |
| Does Not Contain | Response must NOT include the specified text | "error" |
Enter the validation text in the text area. When validation fails, UptimeDock marks the check as down and triggers your configured alerts.
For an authentication endpoint that returns {"result":1,"text":"Success."}on success, set validation to Contains with value"text":"Success." to ensure the login is actually working.
Step 8: Configure Alerts
Expand the Alarms section to configure when you should be notified:
| Alert Type | Description |
|---|---|
| API Down | Triggered when your API is unreachable, returns errors, or fails validation |
| Response Time | Triggered when response time exceeds your specified threshold |
For each alert type, select the notification groups that should receive alerts. You can create notification groups in the Notifications section to define who gets notified via email, SMS, Slack, webhooks, and more.
Step 9: Schedule & Maintenance
Configure when monitoring should run and when to pause for maintenance:
Schedule
By default, monitoring runs 24/7. You can customize the schedule by selecting specific hours and days when monitoring should be active.
Maintenance Windows
Schedule planned maintenance periods when checks should be paused. During maintenance windows:
- No checks will be performed
- No alerts will be triggered
- Uptime statistics won't be affected
This is useful for scheduled deployments or planned API maintenance.
Step 10: Create Your Check
Review your configuration and click the Create button at the bottom of the page. Your API monitoring check will be created and will start collecting data immediately.
Your API monitoring check is now active. Within minutes, you'll see response times, status codes, and validation results on the check's report page.
What's Next?
Now that your API check is running, explore these resources:
- API Monitoring Overview – Learn about all available features
- Website Monitoring – Monitor web pages alongside your APIs