canonical: https://jentic.com/apis/cronitor.io/cronitor # Cronitor API 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. ## For AI agents Create, configure, and control Cronitor monitors for cron jobs and scheduled tasks, plus search and pause monitors via API. ## Scope Does not handle log aggregation, application performance monitoring, or infrastructure metrics - use for cron job and scheduled task monitoring only. ## Capabilities - 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 - Retrieve a single monitor's configuration by monitor key - Update monitor configurations in bulk with a single PUT request ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 your Jentic One instance. The result feeds a weekly reliability summary identifying which monitors are paused, failing, or running late. Example prompt: Use the Jentic SDK to list all Cronitor monitors and group them by paused vs running status for a weekly health summary ## Key endpoints | 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 | ## Key resources - **Monitors** — Create, list, retrieve, update, pause, unpause, and delete monitors individually or in bulk via /monitors and /monitors/{monitorKey} endpoints - **Search** — Run advanced queries across the monitor inventory via the /search endpoint ## Why Jentic - **Setup:** Wiring Cronitor by hand means managing its Basic auth API key and mapping monitor creation, pause, and search calls yourself. Through Jentic you install once, import Cronitor from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Cronitor puts the monitor key in the URL path (/monitors/{monitorKey}), so a rule can pin the agent to the monitors you allow. You choose the operations it may call, so pausing or unpausing a monitor is not included unless you add those operations. - **Credential handling:** Your Cronitor API key is stored once, encrypted, by your own Jentic One instance and injected as the Authorization header at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a cron job monitor' or 'pause a Cronitor monitor', and Jentic returns the matching Cronitor operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **cron-job.org API** — cron-job.org schedules and runs cron jobs in the cloud rather than monitoring jobs running elsewhere - **crowd.dev API** — crowd.dev tracks community activity while Cronitor tracks the scheduled jobs that ingest that data - **Crove API** — Crove generates documents while Cronitor monitors the scheduled tasks that may invoke document generation ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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 your Jentic One instance 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. ### Can I limit what my agent is allowed to do with the Cronitor API? Yes. Because you run Jentic One yourself, your own rules decide which Cronitor operations and which credential the agent may use. Cronitor puts the monitor key in the URL path (/monitors/{monitorKey}), so a rule can pin the agent to only the monitors you allow. You pick the operations it may call, so pausing or unpausing a monitor is excluded unless you explicitly add those endpoints.