Introducing REST API Access: Manage Your Monitors Programmatically

We're excited to announce that UptyBots now provides full REST API access for all users. Whether you're building a custom dashboard, automating monitor creation, or integrating uptime data into your CI/CD pipeline — the API gives you complete control over your monitoring setup.

Why an API?

The UptyBots dashboard is great for day-to-day monitoring. But as your infrastructure grows, you may need to:

Automate monitor creation — spin up monitors for new services or environments automatically
Pull stats into your own dashboards — combine uptime data with your internal metrics
Integrate with CI/CD — create monitors after deployment, pause them during maintenance
Build mobile apps or CLI tools — access your monitoring data from anywhere
Connect with automation platforms — use Zapier, Make, n8n, or custom webhooks to trigger workflows

Getting Started in 3 Steps

Step 1: Create an API Key

Go to Account → API Keys in your dashboard and click "Create Key." Give it a descriptive name (e.g., "CI/CD Pipeline" or "Mobile App"). The key is shown only once — copy it immediately and store it securely.

Step 2: Make Your First Request

Use the key with any HTTP client. Two authentication methods are supported:

## Option 1: X-API-Key header
curl -H "X-API-Key: upty_YOUR_KEY_HERE" \
     https://uptybots.com/api/targets

## Option 2: Bearer header
curl -H "Authorization: Bearer upty_YOUR_KEY_HERE" \
     https://uptybots.com/api/targets

Both methods are equivalent — use whichever your framework or tool expects.

Step 3: Explore the Endpoints

The API covers everything you can do in the dashboard and more:

Monitors — list, create, update, pause/resume, and delete monitors (HTTP, Ping, Port, SSL, Domain, API)
Stats — retrieve hourly and daily uptime and response time data
Incidents — get a history of downtime events
Notifications — list and manage alert notifications
Account — access user info and summary statistics

What Can You Build?

Here are some real-world examples of what our users plan to build with the API:

Custom status dashboards — display uptime stats on a TV screen in your office or embed them in an internal wiki
Deployment automation — your CI/CD pipeline creates a monitor for each new service and pauses it during maintenance windows
Slack/Discord bots — a bot that checks uptime on demand and posts daily summaries to your team channel
Mobile monitoring apps — check your monitors on the go with a native iOS or Android app
Multi-tenant setups — agencies managing multiple client sites can automate monitor provisioning

Response Format

The API returns JSON-LD by default (with pagination metadata like totalItems, first, next, last). If you prefer plain JSON, add the Accept: application/json header.

For write operations, use Content-Type: application/json for POST requests and Content-Type: application/merge-patch+json for PATCH requests.

Security

API keys are stored as SHA-256 hashes — we never keep the plaintext key on our servers. Each key shows only its prefix (e.g., upty_a1b2****) so you can identify which key is which. You can create up to 10 keys per account, rename them, and revoke them at any time.

All API requests are scoped to your account — you can only access your own monitors, stats, and notifications. There's no way to access another user's data through the API.

Full Documentation

For the complete endpoint reference with request examples, filters, and error codes, check out our API Reference page.

We'd love to hear what you build with the API. Have feedback or feature requests? Let us know, or sign up free to get started.