Webhooks

What they are for

A webhook sends an HTTP request to a URL you control as soon as something happens, so you can raise a Slack alert on a bad review or open a ticket without polling. Webhooks are available on the Enterprise plan. With Surveys Pro you can also add endpoints for the Survey due event only, to hand surveys to Zapier, Make or your own code.

Adding an endpoint

1. Go to Settings, then Webhooks.
2. Enter the URL that will receive the requests, such as https://your-app.com/webhooks/dinopix.
3. Choose the events. All are selected by default; pick fewer if you only care about some.
4. Save, then copy the signing secret shown against the endpoint.

The events

• review.created when any new review or comment syncs in.
• review.negative when one arrives that is negative. The usual trigger for an alert.
• order.delivered when an order is marked delivered, which is the normal moment to ask for a review.
• nps.responded when a customer gives an NPS score: the score, its scale and band (low, mid or high), the survey, contact and location. It fires on the score alone, so the comment is usually empty; use survey.answered for what they wrote.
• survey.answered when a customer submits their comment and answers, on any survey: the score and band, the comment, every answer with its question, the survey, contact and location.
• survey.due when a survey that is handed to your webhook is due for a customer (Surveys Pro). Dinopix doesn't email it: you send it, from Zapier, Make or your own code. It carries the contact, the survey, survey_link (add the score on the end, for example survey_link + "9"), survey_urls (one per score), and unsubscribe_url. See Hand surveys to your marketing tool.

A negative review fires both review.created and review.negative. If you subscribe to both, expect two requests and make your handler idempotent.

Verifying the signature

Every request carries a timestamp and a signature:

X-Dinopix-Timestamp: 1790000000
X-Dinopix-Signature: sha256=...

The signature is an HMAC-SHA256, using your endpoint's signing secret, of the timestamp, a full stop, and the raw request body: 1790000000.{"event":...}. Verify it before trusting anything in the payload, and compare using a constant-time comparison rather than string equality.

Then reject the request if the timestamp is more than five minutes from your server's clock. That is what stops someone who has captured a genuine request from sending it to you again later. Each delivery also has a unique X-Dinopix-Delivery id, which you can store to ignore a delivery you have already processed.

Compute the HMAC over the bytes exactly as received. Parsing the JSON and re-serialising it will change the bytes and the signature will not match. This is the single most common reason verification fails.

Deliveries and retries

The endpoint list shows recent deliveries with their status and attempt count. A failed delivery is retried; a persistently failing endpoint shows a rising attempt count, which is your signal that something on your side is down.

Return a 2xx status quickly. Do the real work asynchronously: if your handler is slow, the delivery is treated as failed and retried, and you will process the same event twice.

Turning one off

An endpoint can be deactivated without deleting it, which keeps the configuration and the delivery history while you fix something. Reactivate when you are ready. Deliveries are not queued while it is off.

Changes are logged

Creating, editing and removing endpoints is recorded in the audit log under Webhooks, along with who did it.