Scheduled HTTP requests

Schedule HTTP requests without writing a scheduler

A surprising amount of “background work” is really just an HTTP request that needs to happen on a timer — refresh a cache, hit a rebuild webhook, poke an API, trigger a report. Cronmint lets you schedule any HTTP request (GET, POST, with headers and a body) and runs it for you, with logs and alerts, so you never stand up a scheduler for a one-line job.

When you just need a request on a timer

You do not always need a queue or a worker. Plenty of tasks are a single HTTP call that must repeat on a schedule. Writing and hosting a scheduler for that is overkill; Cronmint makes it a two-field setup.

  • Trigger a rebuild or deploy webhook nightly.
  • Refresh a cache or materialized view every few minutes.
  • Call a third-party API to sync or poll on a cadence.
  • Hit your own endpoint to kick off a batch.

Full control over the request

Set the method, add headers (including auth), and include a JSON body when the endpoint needs one. Cronmint sends exactly the request you configure and records the response.

example
POST https://hooks.yourapp.com/rebuild
Authorization: Bearer <token>
Content-Type: application/json

{ "target": "docs" }

Schedule: 0 * * * *   (hourly)

You still get logs and alerts

Because Cronmint makes the request, it also captures the outcome — status code, response body, and timing — and alerts you when the call fails. A scheduled request you cannot see is a scheduled request you cannot trust.

Schedule an HTTP request free

5 jobs free, no card. Set up your first monitor in about 30 seconds.

Start free

Frequently asked questions

Can I schedule a POST request with a body?

Yes. Cronmint supports GET/POST and other methods, custom headers, and a request body, so you can schedule exactly the HTTP call your endpoint expects.

Do I need a server to schedule HTTP requests?

No. Cronmint hosts the schedule and makes the requests for you — there is nothing to deploy or keep running.

How do I know a scheduled request actually ran?

Every run is logged with its status code, response, and timing, and you get an alert if it fails — so you always have proof it happened.