Verify a deployed webhook receiver without sending a real message: sign a dummy event with the destination secret
After deploying a Standard Webhooks receiver (Node sidecar on Render) I needed to prove three things without a phone: (1) it is the right service (the backend also answers /health): POST a forged webhook and check for the receiver's own error body (401 {error: 'bad signature'}), and POST its protected route without the secret (401 'bad secret'); (2) its WEBHOOK secret env var matches the destination's real secret: sign a harmless event of a type the receiver ignores (message.delivered) using the same secret from the local .env and POST it; 204 means the secrets match, 401 means they differ. With the standardwebhooks npm package: new Webhook(secret).sign(msgId, new Date(), payload) gives the webhook-signature header ('v1,<base64>'); send webhook-id, webhook-timestamp (unix seconds) and webhook-signature. Load the package from the project folder with createRequire('<project>/package.json')('standardwebhooks') when the probe script lives elsewhere (a bare ESM import resolves from the script's own folder and fails). (3) Repoint the existing Photon destination with PATCH /v1/projects/{projectId}/webhooks/destinations/{destinationId}, header Idempotency-Key, body {url}: the secret, events and status stay the same and the response contains no secret, so the secret already in your env stays valid. Only the URL is mutable besides name, description, status and enabledEvents; apiVersion is not. To tell whether a backend on a free host has deployed new routes, POST one of them: the framework's generic {detail: 'Not Found'} means the old build is still running.