Cron-job.org API

Name: Cron-job.org API API
Brand: Cron-job.org API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi Cdbearer7 EndpointsREST

For Agents

Schedule, update, and inspect HTTP-based cron jobs hosted on cron-job.org and pull their execution history.

Quickstart

Get started with Cron-job.org 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:
"schedule a cron job on cron-job.org"

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

Capabilities

What an agent can do with Cron-job.org API API.

Schedule HTTP-based cron jobs against arbitrary URLs without running your own cron daemon

Retrieve full execution history for a job including timing and response status

Update job schedules, URLs, and request settings via PATCH /jobs/{jobId}

Inspect a single execution by identifier to debug a specific failed run

GET STARTED

Start building with Cron-job.org API API

Explore with Jentic

View OpenAPI Document

Use for: I need to schedule a cron job that calls my webhook every hour, List all cron jobs in my cron-job.org account, Get the execution history for a specific cron job, Update the schedule on cron job 12345

Not supported: Does not handle cron-job monitoring of your own infrastructure, log aggregation, or task queue execution — use for hosted HTTP-based scheduled jobs only.

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

Jentic publishes the only available OpenAPI specification for Cron-job.org API, keeping it validated and agent-ready. Cron-job.org is a free hosted cron service that runs scheduled HTTP requests on behalf of users without requiring them to operate a cron daemon. The REST API lets developers create, update, list, and delete jobs, plus inspect each job's execution history with timing and response data. Rate limits are 100 requests per day on the free tier and 5,000 per day for sustaining members, with per-endpoint caps of 5 reads and 1 create per second.

Use Cases

Patterns agents use Cron-job.org API API for, with concrete tasks.

★ Hosted Webhook Scheduling

Replace a self-managed cron server with cron-job.org by registering scheduled HTTP calls through the API. A developer PUTs a new job to /jobs with the target URL, schedule, and request method, and cron-job.org fires the request on schedule. This is ideal for indie projects and side businesses that need reliable scheduling without provisioning a server, and the bearer-token auth model fits cleanly into deploy scripts.

Create a cron job that sends a POST to https://example.com/webhook every 15 minutes using the Authorization header

Execution History Audit

Pull execution history for a specific job via GET /jobs/{jobId}/history to confirm that scheduled runs actually fired and returned the expected status. Teams use this to debug intermittent failures and to produce uptime reports for jobs running on cron-job.org. Individual executions can be drilled into via /jobs/{jobId}/history/{identifier} for response body and timing detail.

Fetch the last 24 hours of execution history for job 12345 and flag any runs with non-2xx response codes

Account Cleanup Within Free-Tier Limits

Stay under the 100-requests-per-day free-tier cap by listing all jobs with GET /jobs, identifying ones that no longer need to run, and deleting them with DELETE /jobs/{jobId}. This is the standard pattern for users who accumulated test jobs while prototyping and need to reclaim their daily quota for real workloads.

List all cron jobs and delete any whose title starts with test- to free up the daily quota

AI Agent Schedule Management

An AI agent on a customer's stack uses Jentic to schedule and manage cron-job.org jobs without ever seeing the bearer token. The agent searches for the cronjoborg_create_job operation, loads the schema, and executes against the customer's vaulted credential. This unlocks scenarios like an agent reading a user's request 'remind my server to refresh its cache every hour' and turning it into a real scheduled job.

Use the Jentic SDK to create a cron-job.org job that calls a refresh URL every hour, returning the new job ID

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for cron-job.

METHOD

PATH

DESCRIPTION

GET

/jobs

List all cron jobs

PUT

/jobs

Create a new cron job

GET

/jobs/{jobId}

Get cron job details

PATCH

/jobs/{jobId}

Update a cron job

DELETE

/jobs/{jobId}

Delete a cron job

GET

/jobs/{jobId}/history

Get job execution history

GET

/jobs/{jobId}/history/{identifier}

Get a single execution detail

GET

/jobs

List all cron jobs

PUT

/jobs

Create a new cron job

GET

/jobs/{jobId}

Get cron job details

PATCH

/jobs/{jobId}

Update a cron job

DELETE

/jobs/{jobId}

Delete a cron job

GET

/jobs/{jobId}/history

Why though Jentic?

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

Credential isolation

The cron-job.org bearer API key is stored encrypted in the Jentic vault. Agents receive a scoped execution token, and Jentic attaches the Authorization: Bearer header at request time so the raw key never enters the agent's context.

Intent-based discovery

Agents search Jentic with intents like 'schedule a webhook every hour' or 'list cron jobs' and Jentic returns the matching cron-job.org operation with its input schema, removing the need to read the cron-job.org docs.

Time to first call

Direct cron-job.org integration: 2-3 hours for bearer auth and job-creation flow. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Cronitor API

Cronitor monitors cron jobs running in your own infrastructure rather than hosting the schedule itself

Pick cron-job.org when the agent needs the cron service to host the schedule. Pick Cronitor when the cron job already runs elsewhere and only needs failure alerting.

Complementary

crowd.dev API

crowd.dev provides community data that scheduled cron-job.org calls can pull and refresh on a schedule

Use cron-job.org to schedule a recurring fetch of crowd.dev community activity into a downstream system.

Complementary

Crove API

Crove generates documents on demand and cron-job.org can fire those generation requests on a schedule

Schedule a cron-job.org call to a Crove document-generation endpoint when an agent needs recurring document output.

FAQs

Specific to using Cron-job.org API API through Jentic.

Why is there no official OpenAPI spec for Cron-job.org API?

cron-job.org does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cron-job.org 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 Cron-job.org API use?

The Cron-job.org API uses bearer-token authentication — clients send their API key as Bearer in the Authorization header. Through Jentic, the bearer token is held encrypted in the vault and injected at request time so the raw key never reaches the agent.

What are the rate limits for the Cron-job.org API?

The default daily rate limit is 100 requests, raised to 5,000 for sustaining members. Per-endpoint caps are 5 requests per second for reads and 1 per second for creates, so bulk job creation needs to be paced.

Can I retrieve the execution history of a specific cron job?

Yes. GET /jobs/{jobId}/history returns the run history for a job, and GET /jobs/{jobId}/history/{identifier} returns the response and timing detail for a single execution.

How do I create a cron job through Jentic?

Search Jentic for 'create a cron job', load the operation schema for PUT /jobs, and execute with the URL, schedule, and request method. The Jentic SDK takes care of bearer-token injection so the agent never handles the key directly.

Can I update an existing cron job's schedule?

Yes. PATCH /jobs/{jobId} accepts a partial update so you can change the schedule, URL, or request method on an existing job without recreating it.