For developers
Build a Webhook Receiver for Testimonials
From Pro, StoryProof sends every new review to a URL you control. If that URL is your own code rather than Zapier or Make, start by recording exactly what arrives. This page deliberately does not describe the request’s fields, headers or signing, because you should build from a real delivery, not from a guess.
- Log first, parse second
- A fast reply, slow work afterwards
- Treat every field as untrusted input
Build checklist
A receiver you can trust with real reviews
Work through it in order. The first group exists so nothing later is built on an assumption.
The checklist runs only in your browser.
The problem, solved
What usually goes wrong with a hand-built receiver
- Problem 1
The code expects fields that never arrive
Field names copied from another vendor’s webhook docs look plausible and fail on the first real request.
How StoryProof solves it
StoryProof sends every new review as it arrives, from Pro. Log one real delivery and write the parser against that, not against a guess.
- Problem 2
The endpoint times out on busy days
Sending emails or uploading files inside the request handler makes every delivery slow.
How StoryProof solves it
Store and acknowledge first, then process. Reviews keep arriving one at a time as customers submit them, and a quick reply keeps the receiver ready for the next.
- Problem 3
Anyone could post fake reviews to the endpoint
A public URL that writes to your database invites junk.
How StoryProof solves it
Keep the URL secret and validate input. Even if a fake entry got in, nothing appears on your site until a person approves it in StoryProof.
- Problem 4
We only wanted reviews on our website
Writing a receiver to rebuild a display layer is a lot of work for what an embed already does.
How StoryProof solves it
A widget needs two lines of HTML, a div with the widget id and the async embed.js script, so keep the receiver for back-office jobs.
- Problem 5
The developer needs workspace access to test
Handing over an admin login for one webhook is more access than the job needs.
How StoryProof solves it
Roles and permissions, on every plan, can give the developer only the parts of the workspace they need.
A first receiver that only records
Sample code for logging, not a StoryProof payload reference
const express = require('express');
const app = express();
app.post('/hooks/reviews/<long-random-segment>', express.json(), (req, res) => {
console.log(req.headers['content-type'], JSON.stringify(req.body));
res.sendStatus(200);
});
app.listen(3000);
It assumes nothing about the fields. Once you have saved a few real deliveries, replace the console line with validated processing.
In StoryProof
Ship it in four stages
Step 1 of 4
Deploy the recording route
Log method, headers and body; reply with a 2xx status.
Step 2 of 4
Register and capture samples
Add the URL where StoryProof lists webhooks and leave a few test reviews of different kinds.
Step 3 of 4
Write the parser from the samples
Validate each field you saw, escape text, and decide what to do when an expected field is missing.
Step 4 of 4
Move work out of the request
Queue processing, make it safe to repeat, and keep logging failures where someone will see them.
Before you start
What this page will not tell you
No payload reference
Field names, event names, headers, retries and signatures are not described here. Inspect a real delivery.
No signing scheme is claimed
Do not implement verification for an algorithm you have not seen documented by StoryProof.
Webhooks need the right plan
They start on Pro. Below that, the in-app alert is the signal.
Express details are from its docs
The parser notes follow the Express 5 API reference as of 2026-11-17. Other frameworks behave differently.
FAQ
Questions people ask
Short answers to what usually comes up next.
What does the StoryProof webhook payload look like?
This page does not describe it, on purpose. Register a logging endpoint, leave a test review and read what arrives.
Does StoryProof retry a failed delivery?
That is not stated here. Build the receiver so a repeat is harmless and a failure is logged, and you are covered either way.
Should the receiver approve reviews automatically?
No. Approval is a decision made in StoryProof. The receiver should treat every incoming review as unapproved.
Can I use a serverless function instead of Express?
Yes. The same order applies on any platform: record, parse from samples, validate, acknowledge fast.
Still have a question? Ask the StoryProof team or book a demo.
Receive every new review in your own system
Collect with StoryProof, point the webhook at your endpoint, and build from what really arrives.