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

# StatusCake API

StatusCake provides website monitoring services. The API allows programmatic management of uptime checks, SSL checks, pagespeed checks, heartbeat checks, maintenance windows, and contact groups. The API exposes 29 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create uptime check, list uptime checks. Covers 29 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create uptime check
- List uptime checks
- Get uptime check
- Update uptime check
- Delete uptime check

## Use cases

### CRM Operations

Use the StatusCake API to perform crm operations programmatically. The API provides 29 endpoints covering core functionality including create uptime check, list uptime checks, get uptime check.

Example prompt: Call POST /uptime to create uptime check

### Automated Contact Groups Management

Automate contact groups operations by combining multiple StatusCake API endpoints. Agents can list uptime checks and then get uptime check in a single workflow.

Example prompt: Call GET /uptime to list uptime checks, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call StatusCake 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 'create uptime check', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/uptime` | Create uptime check |
| GET | `/uptime` | List uptime checks |
| GET | `/uptime/{testId}` | Get uptime check |
| PUT | `/uptime/{testId}` | Update uptime check |
| DELETE | `/uptime/{testId}` | Delete uptime check |
| GET | `/uptime/{testId}/history` | Get uptime check history |
| GET | `/uptime/{testId}/periods` | Get uptime check periods |
| GET | `/uptime/{testId}/alerts` | Get uptime check alerts |

## Key resources

- **Contact Groups** — Operations related to Contact Groups
- **Heartbeat** — Operations related to Heartbeat
- **Locations** — Operations related to Locations
- **Maintenance** — Operations related to Maintenance
- **Pagespeed** — Operations related to Pagespeed

## Why Jentic

- **Setup:** Wiring the StatusCake API by hand means setting up its Authorization header key, mapping the uptime test endpoints, and threading the test id through history, periods and alerts calls yourself. Through Jentic you install once, import the StatusCake API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** StatusCake puts the test id in the URL path (`/uptime/{testId}`, `/uptime/{testId}/history`), so a rule can pin your agent to one uptime test: it can read that test's history, periods and alerts and nothing else. You choose the operations it may call, so deleting a test is not included unless you add it.
- **Credential handling:** Your StatusCake 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 'create an uptime check' or 'read a test's uptime history', and Jentic returns the matching StatusCake API 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 StatusCake API use?

The StatusCake API uses an API key passed 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 create uptime check with the StatusCake API?

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

### What are the rate limits for the StatusCake 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 create uptime check through Jentic?

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

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

The StatusCake API exposes 29 endpoints covering contact groups, heartbeat, locations operations.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which StatusCake operations and credentials your agent can use. StatusCake carries the test id in the URL path, such as `/uptime/{testId}` and `/uptime/{testId}/history`, so you can pin an agent to a single uptime test and let it read only that test's history, periods, and alerts. You choose exactly which operations it may call, so destructive actions like deleting a test stay off limits unless you grant them.