canonical: https://jentic.com/apis/uptimerobot.com/uptimerobot

# UptimeRobot API

UptimeRobot monitors websites and services for uptime. The API provides operations for managing monitors, alert contacts, maintenance windows, and public status pages. The API exposes 18 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get monitors, create a monitor. Covers 18 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Get monitors
- Create a monitor
- Edit a monitor
- Delete a monitor
- Reset a monitor

## Use cases

### CRM Operations

Use the UptimeRobot API to perform crm operations programmatically. The API provides 18 endpoints covering core functionality including get monitors, create a monitor, edit a monitor.

Example prompt: Call POST /getMonitors to get monitors

### Automated Account Management

Automate account operations by combining multiple UptimeRobot API endpoints. Agents can create a monitor and then edit a monitor in a single workflow.

Example prompt: Call POST /newMonitor to create a monitor, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call UptimeRobot API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get monitors', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /getMonitors | Get monitors |
| POST | /newMonitor | Create a monitor |
| POST | /editMonitor | Edit a monitor |
| POST | /deleteMonitor | Delete a monitor |
| POST | /resetMonitor | Reset a monitor |
| POST | /getAlertContacts | Get alert contacts |
| POST | /newAlertContact | Create an alert contact |
| POST | /editAlertContact | Edit an alert contact |

## Key resources

- **Account** — Operations related to Account
- **Alert Contacts** — Operations related to Alert Contacts
- **Maintenance Windows** — Operations related to Maintenance Windows
- **Monitors** — Operations related to Monitors
- **Status Pages** — Operations related to Status Pages

## Why Jentic

- **Setup:** Wiring the UptimeRobot API by hand means passing your API key on every POST, learning its form-style request bodies, and paging through monitors and alert contacts yourself. Through Jentic you install once, import UptimeRobot from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** UptimeRobot addresses its monitors through POST bodies rather than the URL path, so limit the agent to the operations it needs, such as getMonitors and editMonitor. You choose that operation set, so destructive ones like deleteMonitor are not included unless you add them.
- **Credential handling:** Your UptimeRobot API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get monitors' or 'create a new monitor', and Jentic returns the matching UptimeRobot operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the UptimeRobot API use?

The UptimeRobot API uses an API key passed in the `api_key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get monitors with the UptimeRobot API?

Yes. Use the POST /getMonitors endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the UptimeRobot API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get monitors through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get monitors'. Jentic returns the matching UptimeRobot API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the UptimeRobot API have?

The UptimeRobot API exposes 18 endpoints covering account, alert contacts, maintenance windows operations.

### Can I limit what my agent is allowed to do with the UptimeRobot API?

Yes. Because you run Jentic One yourself, you decide which UptimeRobot operations the agent can call and which credentials it may use. UptimeRobot addresses its monitors through POST bodies rather than the URL path, so you scope by operation set, for example allowing getMonitors and editMonitor while leaving destructive calls like deleteMonitor out unless you add them. Your rules are enforced at execution time, and the API key is injected then rather than exposed to the agent.