cronmint

REST API · v1

Automate all of Cronmint

Create, update, pause, run, and delete HTTP cron jobs and heartbeat monitors. Read execution evidence and record heartbeat pings from any agent or script.

Authentication

Send your key as a bearer token. Keys carry full account access, are shown once, and are stored hashed at rest.

curl https://www.cronmint.com/api/v1/me \
  -H "Authorization: Bearer $CRONMINT_API_KEY"

Create an HTTP cron job

Use a stable clientRequestId. Repeating the request with the same value returns the existing job instead of creating a duplicate.

curl -X POST https://www.cronmint.com/api/v1/jobs \
  -H "Authorization: Bearer $CRONMINT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "http",
    "name": "Weekday sync",
    "url": "https://example.com/api/sync",
    "method": "POST",
    "headers": {"Content-Type": "application/json"},
    "requestBody": "{\"source\":\"cronmint\"}",
    "scheduleCron": "0 9 * * 1-5",
    "timezone": "Asia/Kolkata",
    "retryAttempts": 1,
    "clientRequestId": "codex:example:weekday-sync"
  }'

Create a heartbeat monitor

The response includes an unguessable public pingUrl. Have the monitored process call it after each successful run. API-key-authenticated pings are also available at POST /jobs/{jobId}/ping.

curl -X POST https://www.cronmint.com/api/v1/jobs \
  -H "Authorization: Bearer $CRONMINT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "heartbeat",
    "name": "Nightly database backup",
    "expectedIntervalSeconds": 86400,
    "gracePeriodSeconds": 3600,
    "alertEmail": "ops@example.com",
    "clientRequestId": "codex:example:nightly-backup"
  }'

Agent discovery

Agents should read the live OpenAPI document before acting. It contains the complete request schemas and all endpoints for CRUD, run, test, ping, and execution history.

OpenAPI: https://www.cronmint.com/api/v1/openapi.json
Discovery: https://www.cronmint.com/api/v1

Recommended agent instruction:
"Read the Cronmint OpenAPI contract, authenticate with the provided key,
use stable clientRequestId values, and never print or commit the key."