ping

A ping is a small signed event that the Routeur team can queue for any active subscription on request. It travels through the same outbox, signing, retries and timeouts as a real alert, so a ping that verifies means real alerts will too. It is the PingEvent schema in the API reference.

Example delivery

POST /routeur HTTP/1.1
Host: hooks.example.com
Content-Type: application/json
User-Agent: Routeur-Webhooks/1
Routeur-Delivery: 48190
Routeur-Signature: t=1790532000,v1=cfd593e17f96f36e56761f9b2c023626d56119e33f7f497c276e02b43c6b54f3

{"type":"ping","version":"2026-09-15","created_at":"2026-09-27T18:00:00Z","subscription":"sub_k3m8x2p9q7w1e5r4"}

That signature is real: it is HMAC-SHA256 of 1790532000. followed by the body above, exactly as printed on one line, with the key whsec_0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef. Feed those three inputs to your verifier to check it before your first delivery.

SECRET=whsec_0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef
BODY='{"type":"ping","version":"2026-09-15","created_at":"2026-09-27T18:00:00Z","subscription":"sub_k3m8x2p9q7w1e5r4"}'
printf '%s.%s' 1790532000 "$BODY" | openssl dgst -sha256 -hmac "$SECRET"
# cfd593e17f96f36e56761f9b2c023626d56119e33f7f497c276e02b43c6b54f3

Fields

Field	Type	Meaning
`type`	`"ping"`	Branch on this.
`version`	string	The event shape version, the same value real alerts carry (currently `2026-09-15`).
`created_at`	timestamp	When the ping was queued, RFC 3339 in UTC.
`subscription`	string	The subscription the ping was sent for, `sub_` and 16 lowercase letters and digits. Check it against the one you were given: it confirms which secret should verify the delivery.

There is no graph_run and no lead. Slack subscriptions receive {"text": "Routeur alerts are connected. Executable mispricings will be posted here."} instead.

Triggering a ping

Pings are queued by the Routeur team, not through the API. Send them your subscription id and ask for a test delivery. The ping is queued at once and delivered by the next run of the delivery job, so it arrives within about two minutes. What happens then follows the delivery rules exactly:

Your response	Outcome
`2xx`	Delivered. The team can see it on the subscription’s delivered count.
`410 Gone`	The subscription is disabled, even for a ping.
Anything else, a timeout or a connection error	Retried with the same backoff as real alerts, up to 8 attempts.

A ping is not subject to the six-hour repeat window and does not affect it; you can ask for as many as you need while setting up.

Handling

Verify the signature, record Routeur-Delivery, respond 2xx, and do nothing else. A handler that only knows lead.executable must still acknowledge a ping, or the ping will be retried and eventually marked failed.

event = json.loads(raw_body)
if event["type"] == "ping":
    log.info("Routeur webhook connected for %s", event["subscription"])
elif event["type"] == "lead.executable":
    handle_lead(event)
else:
    log.warning("unknown Routeur event type %s", event["type"])

Verifying signatures: the algorithm and tested verifiers in Python, Node and Go.
Webhooks overview: getting a subscription, retries, disabling.
lead.executable: the event you are setting up to receive.

Get started

Concepts

Agents & MCP

Webhooks

Reference

Example delivery

Fields

Triggering a ping

Handling

Example delivery

Fields

Triggering a ping

Handling

Related