curl guide

Ping Verifagent with curl

curl is the smallest portable client. Use it to test a monitor or as the final step of any shell pipeline.

Before you start

Create a monitor with your workflow’s real frequency, then copy its URL from the dashboard. Its token is secret: do not publish it.

Module to use : curl. Place it after the last useful action on the success path.

Setup

Copy the monitor URL

Paste your monitor URL below. The token is secret — treat it like a password.

https://verifagent.com/api/ping/your-ping-token

GET with -fsS (recommended)

-f fails on HTTP errors, -s stays quiet, -S still shows errors. Chain after your command with &&.

# After a successful command only
my-command && curl -fsS "https://verifagent.com/api/ping/your-ping-token"

# Standalone test
curl -fsS "https://verifagent.com/api/ping/your-ping-token"

POST variant

POST is accepted the same way as GET for a plain heartbeat. Useful when a tool only allows POST.

curl -fsS -X POST "https://verifagent.com/api/ping/your-ping-token"

# Optional JSON body (stored as metadata — do not send secrets)
curl -fsS -X POST "https://verifagent.com/api/ping/your-ping-token" \
  -H "Content-Type: application/json" \
  -d '{"source":"shell"}'

Read the response

A healthy monitor returns HTTP 200 and {"ok":true}. Then check the dashboard status.

{"ok":true}

Always place curl after success. For one-shot tests any period works; for production, match period to the real schedule and keep a small grace window.

Available routes

The base URL is enough for a heartbeat. Variants enrich history if your platform has several branches.

GET https://YOUR_PING_URL

POST https://YOUR_PING_URL/success

POST https://YOUR_PING_URL/fail?msg=Error

Verify

Run the GET example, confirm {"ok":true}, then open the monitor — status Up and a fresh last-signal timestamp.

Expected response: 200 {"ok":true}. The monitor moves from Pending to Up.