Checking your receiver with PING

A PING is a signed delivery with no business data. It is the safe way to check your receiver before real events reach it.

Ask for a PING

Ask your RaviFurnitures contact to send one. In the admin portal they open System → Settings (the Webhooks & API keys page) and press the paper-plane button (Send test event) next to your webhook. Staff with MANAGE_WEBHOOKS can also send one through the API.

The PING goes to that webhook even if PING is not among its events. The webhook must be switched on.

What arrives

POST /your/webhook/path HTTP/1.1
Content-Type: application/json
X-RaviFurniture-Event: PING
X-RaviFurniture-Signature: 9b0e…(64 lowercase hex characters)

{"data":{"message":"RaviFurniture webhook test"},"event":"PING","timestamp":"2026-10-17T04:45:02.123456+00:00","version":"1"}

It is signed with your webhook’s secret, like every other delivery. It is delivered and retried exactly like a real event: first attempt about a second after staff press the button, then retries about 3 minutes apart if your receiver fails.

What your receiver should do

1. Verify the signature over the raw body (see Verifying signatures).
2. Answer with a 2xx status within 10 seconds.
3. Recognise event: "PING" and do no business processing for it.

Each PING has a new timestamp, so its body differs from the last one. Your duplicate check won’t swallow a second PING.

Reading the result

The Webhooks list on the same admin page shows the five most recent deliveries for each webhook:

• the event type and the time of the latest attempt,
• the number of attempts,
• a badge with the HTTP status your server returned, or PENDING or FAILED when there was no response. Green means success, amber means waiting for a retry, red means failed.

RaviFurnitures also stores the first 1,024 characters of your response body, or the connection error when there was no response. That isn’t shown on the page; ask your contact if you need it.

What staff see	What it means
200 badge (green), 1 attempt	Your receiver accepted the PING.
401 badge	Your receiver rejected the signature. Check you use the right secret, as text, over the raw body.
3xx badge	Your URL redirects, and redirects are not followed. Ask for the exact final URL to be set.
PENDING or FAILED, no status code	We could not connect, the TLS certificate was not accepted, or you took longer than 10 seconds.

A delivery shows FAILED after its third failed attempt; one more attempt still follows about 3 minutes later.

Before real events

• A PING verifies and gets a 2xx.
• A delivery with a wrong signature is rejected. You can check this locally with the tested samples.
• You store deliveries before answering, and process them afterwards.
• Duplicates are dropped by body hash, and writes are upserts.
• You have a reconciliation job for your integration.