Cron-job.org API

Name: Cron-job.org 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.

Install Jentic One Beta

Connect the Cron-job.org API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cron-job.org API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcronjoborg%2Fcronjoborg" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcronjoborg%2Fcronjoborg" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Cron-job.org 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}

GET STARTED

Start building with Cron-job.org API

Explore with Jentic One

View OpenAPI Document

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 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 Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring cron-job.org by hand means managing its bearer API key and mapping job creation, update, and history calls against api.cron-job.org yourself. Through Jentic you install once, import cron-job.org from the API Directory, store the key once, and your agent calls it.

Permission scoping

cron-job.org puts the job id in the URL path (/jobs/{jobId}), so a rule can pin the agent to the jobs you allow. You choose the operations it may call, so deleting a job is not included unless you add that operation.

Credential isolation

Your cron-job.org API key is stored once, encrypted, by your own Jentic One instance and attached as the Authorization Bearer header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'schedule a webhook every hour' or 'list cron jobs', and Jentic returns the matching cron-job.org operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Cron-job.org 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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Cron-job.org API?

Yes. Jentic One is self-hosted, so your own rules decide which cron-job.org operations the agent may call and which credential it uses. You can allow it to list and create jobs with GET /jobs and PUT /jobs while excluding DELETE /jobs/{jobId} so it can never remove a job unless you add that operation. Because the job id lives in the URL path at /jobs/{jobId}, you can also pin the agent to only the specific jobs you permit.

Cron-job.org API

Connect the Cron-job.org API to your agent

Capabilities

Start building with Cron-job.org API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs