Skip to main content

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.

Observe before you code
Parse and validate
Reply fast, work later
Protect the URL

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.

  • Problem 2

    The endpoint times out on busy days

    Sending emails or uploading files inside the request handler makes every delivery slow.

  • Problem 3

    Anyone could post fake reviews to the endpoint

    A public URL that writes to your database invites junk.

  • 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.

  • Problem 5

    The developer needs workspace access to test

    Handing over an admin login for one webhook is more access than the job needs.

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.

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.

Sources

  1. express() API reference: express.json, Express. Checked 2026-11-17.

Last updated 2026-11-17.