Heartbeat after a cron job finishes
The simplest integration. Exit successfully, then hit the ping URL.
0 * * * * /path/to/backup.sh && curl -fsS -m 10 --retry 3 https://hc.bestboy.work/ping/your-uuid-here
Classic /docs/ remains available as the full reference. This newer layer reorganizes the
product around concrete tasks: getting started, wiring heartbeats, using the Management API, validating
alerts, and selecting the right monitoring pattern for a real job.
The simplest integration. Exit successfully, then hit the ping URL.
0 * * * * /path/to/backup.sh && curl -fsS -m 10 --retry 3 https://hc.bestboy.work/ping/your-uuid-here
Useful when you want runtime measurements and explicit failure signals.
curl -fsS -m 10 --retry 3 "https://hc.bestboy.work/ping/your-uuid-here/start"
run_the_job
status=$?
curl -fsS -m 10 --retry 3 "https://hc.bestboy.work/ping/your-uuid-here/$status"
exit $status
Provision checks from your backend or automation scripts.
curl -X POST https://hc.bestboy.work/api/v3/checks/ \
-H "X-Api-Key: your-api-key" \
-H "Content-Type: application/json" \
-d '{
"name": "Nightly backup",
"slug": "nightly-backup",
"tags": "ops backup",
"timeout": 900,
"grace": 300
}'
A tiny requests-based example for internal tools.
import requests
url = "https://hc.bestboy.work/ping/your-uuid-here"
response = requests.get(url, timeout=10)
response.raise_for_status()
Start here when the question is scenario-based: cron jobs, backups, CI, workers, or alert delivery.
Use the AI pages when you need a compressed product model, machine-readable links, or OpenAPI discovery.
Use /docs/ as the full reference when you need the complete detail set or legacy topic coverage.