HTTP Request

Every time a cron job fires, QuzenixCron sends an HTTP request to the URL you configured. Here's exactly what gets sent and what counts as a successful response.

Supported Methods

QuzenixCron supports 6 standard HTTP methods:

  • GET — most common for keepalive and polling
  • POST — send a payload (Discord webhooks, API calls)
  • PUT
  • PATCH
  • DELETE
  • HEAD — health check without a body

Headers

Add custom headers in the form as key-value pairs. Total header size is capped at 8 KB. These headers are added automatically:

User-Agent: QuzenixCron/1.0
Accept: */*

You can override these freely. Common headers people use:

Content-Type: application/json
Authorization: Bearer xxxxxxxxxxxx
X-API-Key: your-key-here
X-Request-Source: cron

Request Body

The body is only sent for methods that support it (POST/PUT/PATCH). Max size is 100 KB.

{
  "event": "scheduled-trigger",
  "timestamp": "{{now}}"
}
Template variables
Bodies are sent as-is — placeholders like {{now}}won't be substituted. If you need dynamic values, have your endpoint resolve them.

Timeout

Each job has its own timeout (1–120 seconds, default 30). If the target doesn't respond in time, the request is aborted and the execution is marked as timeout. Set it lower for fast endpoints so retries kick in sooner.

What Counts as Success

HTTP StatusExecution Status
2xx (200, 201, 204, ...)success
3xx (redirect)success (follows redirect)
4xx / 5xxfailed
Connection refused / DNS errorfailed
No response within timeouttimeout

What Gets Stored

For auditing and debugging, QuzenixCron logs the following for every execution:

  • HTTP status code
  • Response headers
  • Response body (first 10 KB)
  • Total duration (ms)
  • Error message (if any)
PreviousCron ExpressionsNext Authentication