Reviewflowz API Get an API key

Webhooks

Get new reviews, replies and requests pushed to your URL.

We POST an event to your URL when something happens: a new review, a reply going live, a request bouncing. Pick the events per endpoint, in the app (Integrations > Webhooks) or with Create an endpoint, whose answer has the endpoint's signing secret (whsec_...). Events lists every event we send, with an example of each.

What you receive

{"id": "evt_4821","type": "review.created","timestamp": "2026-11-10T08:40:09Z","data": {"object": {"id": "rev_918273","platform": "google_maps","rating": 5,"text": "Booked the summit tickets online and skipped the whole queue.","reviewer": { "name": "Maya Chen" },"date": "2026-11-09T18:32:00Z"},"source": "src_4812"}}​

data.object is shortened here: it's the full subject as the API returns it at send time. Something deleted comes as { "id": "...", "deleted": true }.

Check the signature

Every request carries three headers (Standard Webhooks): webhook-id, webhook-timestamp and webhook-signature. Sign id.timestamp.body with HMAC-SHA256, keyed with the base64-decoded part of the secret after whsec_, and compare it with each v1, value in the header. Use the raw body, before you parse it. Refuse timestamps more than 5 minutes old.

import base64, hashlib, hmac, time​def verify(secret, headers, body):key = base64.b64decode(secret.removeprefix("whsec_"))signed = f"{headers['webhook-id']}.{headers['webhook-timestamp']}.{body}".encode()expected = "v1," + base64.b64encode(hmac.new(key, signed, hashlib.sha256).digest()).decode()fresh = abs(time.time() - int(headers["webhook-timestamp"])) < 300return fresh and any(hmac.compare_digest(expected, s) for s in headers["webhook-signature"].split(" "))​

The Standard Webhooks libraries do the same check in one call.

Answer fast, expect repeats

  • Answer 2xx within 10 seconds. Do the work after answering.
  • Retries: anything else is tried again after 5s, 5m, 30m, 2h, 5h, 10h and 10h: 8 tries over about 27 hours.
  • At least once: the same event can arrive twice. Skip an id you've already handled.
  • Order isn't guaranteed. Use timestamp and the object's own fields. Review, rating and tag events, and skipped or failed requests, arrive within about two minutes of the change; the others within seconds.

When your endpoint keeps failing

After 3 days of nothing but failures we email the endpoint's creator and the account owner. After 5, we switch the endpoint off and email again. An endpoint that answers 410 Gone is switched off at once.

Switch it back on in the app, or PATCH /v3/webhook-endpoints/{id} with { "status": "active", "replay": true } to also get every event it missed, or "replay": false to skip them.

Test, resend, rotate

  • POST /v3/webhook-endpoints/{id}/test sends a signed sample now and returns your endpoint's answer.
  • GET /v3/events lists the last 30 days of events with their delivery attempts. POST /v3/events/{id}/redeliver sends one again.
  • POST /v3/webhook-endpoints/{id}/rotate-secret issues a new secret. The old one keeps signing too for 24 hours, so both signatures are in the header while you switch.
What it does Call
List endpoints GET /v3/webhook-endpoints
Create an endpoint POST /v3/webhook-endpoints
Get an endpoint GET /v3/webhook-endpoints/{id}
Update an endpoint PATCH /v3/webhook-endpoints/{id}
Delete an endpoint DELETE /v3/webhook-endpoints/{id}
Send a test event POST /v3/webhook-endpoints/{id}/test
Rotate the secret POST /v3/webhook-endpoints/{id}/rotate-secret
List events GET /v3/events
Get an event GET /v3/events/{id}
Resend an event POST /v3/events/{id}/redeliver
List event types GET /v3/event-types
Events Every event we send, with an example.