Cronitor API

Name: Cronitor API API
Brand: Cronitor API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilitybasic9 EndpointsREST

For Agents

Create, configure, and control Cronitor monitors for cron jobs and scheduled tasks, plus search and pause monitors via API.

Quickstart

Get started with Cronitor API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a cron job monitor in Cronitor"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Cronitor API API.

Create individual or bulk monitors for cron jobs, websites, and background workers

Pause and unpause specific monitors during planned maintenance windows

Run advanced search queries across the full monitor inventory

Bulk delete obsolete monitors after deprecating scheduled jobs

GET STARTED

Start building with Cronitor API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Cronitor API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Cronitor API, keeping it validated and agent-ready. Cronitor is a monitoring service that tracks cron jobs, scheduled tasks, websites, and background processes, alerting teams when expected runs fail or run late. The API lets developers create and configure monitors, send heartbeat telemetry, run advanced searches, and pause or resume checks programmatically. It supports bulk monitor management for teams running hundreds of scheduled jobs across multiple environments.

Use Cases

Patterns agents use Cronitor API API for, with concrete tasks.

★ Cron Job Failure Alerting

Wrap every scheduled cron job and background worker with a Cronitor monitor so the team is alerted when a run fails, runs too long, or skips entirely. Engineers POST to /monitors with the expected schedule and notification rules, then point the cron job's success and failure callbacks at Cronitor's telemetry endpoints. This catches silent failures that traditional logging misses, and the bulk PUT /monitors call lets a deployment script keep monitor definitions in sync with the actual crontab.

Create a Cronitor monitor named nightly-backup with schedule 0 2 * * * and email notifications on failure

Maintenance Window Pause Automation

Suppress noisy alerts during planned maintenance by pausing affected monitors before deployment and unpausing them once the system is healthy again. A deployment pipeline calls PUT /monitors/{monitorKey}/pause for each monitor in the affected service, runs the migration, then calls /unpause to restore alerting. This avoids on-call fatigue from expected downtime without permanently disabling monitors.

Pause monitor with key db-migration-job before a database migration starts and unpause it after the migration completes

Inventory Search and Cleanup

Audit a large Cronitor account by running advanced searches against /search to find monitors by tag, name pattern, or status, then bulk-delete obsolete entries with DELETE /monitors. Teams with hundreds of monitors accumulated over years use this to remove monitors tied to decommissioned services and reduce monthly billing tied to monitor count.

Search for monitors tagged legacy-service and bulk delete the matching monitor keys

AI Agent Reliability Reporting

An AI agent surfaces the current state of a customer's scheduled-job estate by calling Cronitor through Jentic. The agent searches Jentic for the cronitor_list_monitors operation, loads the schema, and executes against the customer's basic-auth credential stored in the Jentic vault. The result feeds a weekly reliability summary identifying which monitors are paused, failing, or running late.

Use the Jentic SDK to list all Cronitor monitors and group them by paused vs running status for a weekly health summary

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for cronitor api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/monitors

List all monitors

POST

/monitors

Create a single monitor

PUT

/monitors

Create or update monitors in bulk

GET

/monitors/{monitorKey}

Get a specific monitor by key

PUT

/monitors/{monitorKey}/pause

Pause a monitor

PUT

/monitors/{monitorKey}/unpause

Unpause a monitor

GET

/search

Advanced search across monitors

GET

/monitors

List all monitors

POST

/monitors

Create a single monitor

PUT

/monitors

Create or update monitors in bulk

GET

/monitors/{monitorKey}

Get a specific monitor by key

PUT

/monitors/{monitorKey}/pause

Pause a monitor

PUT

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Cronitor basic-auth API key is stored encrypted in the Jentic vault. Agents receive a scoped execution token, and Jentic injects the Authorization header at request time so the raw key never enters the agent's context.

Intent-based discovery

Agents search Jentic with intents like 'create a cron job monitor' or 'pause a Cronitor monitor' and Jentic returns the matching Cronitor operation with its input schema, removing the need to read Cronitor's docs.

Time to first call

Direct Cronitor integration: half a day to set up basic-auth and wire up monitor creation. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

cron-job.org API

cron-job.org schedules and runs cron jobs in the cloud rather than monitoring jobs running elsewhere

Choose cron-job.org when the agent needs to host the schedule itself. Choose Cronitor when the cron job already runs in the customer's infrastructure and only needs observability.

Complementary

crowd.dev API

crowd.dev tracks community activity while Cronitor tracks the scheduled jobs that ingest that data

Pair Cronitor with crowd.dev when an agent needs to verify that the nightly community-data ingestion job actually ran before reporting on community metrics.

Complementary

Crove API

Crove generates documents while Cronitor monitors the scheduled tasks that may invoke document generation

Use Cronitor alongside Crove to confirm that a recurring document-generation cron is firing on schedule.

FAQs

Specific to using Cronitor API API through Jentic.

Why is there no official OpenAPI spec for Cronitor API?

Cronitor does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cronitor API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Cronitor API use?

The Cronitor API uses HTTP Basic Auth with the API key supplied as the username and an empty password. When called through Jentic, the API key is stored encrypted in the Jentic vault and never appears in the agent's context — Jentic injects it into the Authorization header at execution time.

Can I pause a Cronitor monitor during a deployment?

Yes. Call PUT /monitors/{monitorKey}/pause to suppress alerts while a planned change is in flight, then call PUT /monitors/{monitorKey}/unpause once the system is healthy. This is the recommended pattern for avoiding alert noise during scheduled maintenance.

How many endpoints does the Cronitor API expose?

The Cronitor API exposes 9 endpoints covering monitor CRUD operations, bulk create/update/delete, pause and unpause controls, and an advanced /search endpoint for querying the monitor inventory.

How do I create a monitor through Jentic?

Search Jentic for 'create a Cronitor monitor', load the operation schema for POST /monitors, and execute with the monitor's name, schedule, and notification settings. The Jentic SDK handles credential injection and request signing automatically.

Can I bulk-update monitors in a single request?

Yes. PUT /monitors accepts an array of monitor definitions and creates or updates them in one call, which is useful for keeping Cronitor in sync with a checked-in cron configuration during deploys.