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

# Site24x7 API

REST API for Site24x7 website and infrastructure monitoring platform. Manage monitors, monitor groups, MSP customers, and retrieve monitoring data. The API exposes 11 endpoints secured with bearer authentication.

## For AI agents

Programmatically get device key, create monitor. Covers 11 operations with bearer authentication.

## Scope

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

## Capabilities

- Get device key
- Create monitor
- List all monitors
- Update monitor
- Delete monitor

## Use cases

### Developer Tools Operations

Use the Site24x7 API to perform developer tools operations programmatically. The API provides 11 endpoints covering core functionality including get device key, create monitor, list all monitors.

Example prompt: Call GET `/api/device_key` to get device key

### Automated Device_Key Management

Automate device_key operations by combining multiple Site24x7 API endpoints. Agents can create monitor and then list all monitors in a single workflow.

Example prompt: Call POST `/api/monitors` to create monitor, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Site24x7 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 bearer tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/device_key` | Get device key |
| POST | `/api/monitors` | Create monitor |
| GET | `/api/monitors` | List all monitors |
| GET | `/api/monitors/{monitor_id}` | Get monitor |
| PUT | `/api/monitors/{monitor_id}` | Update monitor |
| DELETE | `/api/monitors/{monitor_id}` | Delete monitor |
| POST | `/api/monitor_groups` | Create monitor group |
| GET | `/api/monitor_groups` | List monitor groups |

## Key resources

- **Device_Key** — Operations for device_key
- **Monitor_Groups** — Operations for monitor_groups
- **Monitor_Type_Constants** — Operations for monitor_type_constants
- **Monitors** — Operations for monitors
- **Short** — Operations for short

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 70 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 77 / 100
- **View full report:** https://jentic.com/apis/site24x7.com/site24x7/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Site24x7 API by hand means setting up its Zoho OAuth bearer token and carrying it across every monitor and monitor-group call yourself. Through Jentic you install once, import Site24x7 from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Site24x7 puts the monitor id in the URL path (`/api/monitors/{monitor_id}`), so a rule can pin your agent to one monitor: it can read and update that monitor and nothing else. You choose the operations it may call, so destructive ones like deleting a monitor are not included unless you add them.
- **Credential handling:** Your Site24x7 token 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 the device key' or 'create a monitor', and Jentic returns the matching Site24x7 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Site24x7 API use?

The Site24x7 API uses a Bearer token in the Authorization 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 device key with the Site24x7 API?

Yes. Use the GET `/api/device_key` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Site24x7 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 device key through Jentic?

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

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

The Site24x7 API exposes 11 endpoints covering device_key, monitor_groups, monitor_type_constants operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Site24x7 operations and credentials the agent may use. Site24x7 puts the monitor id in the URL path (`/api/monitors/{monitor_id}`), so you can pin the agent to a single monitor and allow only read and update on it. You choose the operations it may call, so destructive ones such as DELETE `/api/monitors/{monitor_id}` or creating monitor groups stay off unless you add them.