How Do I Test My Feedspace Webhook Integration?

Overview

Before connecting your production server, you can test your Feedspace webhook integration using a free temporary URL service. This lets you inspect the exact JSON payload Feedspace sends, confirm your event selection is correct, and validate your signature verification code, all without writing a single line of server code first.

What You Need

• A free account at webhook.site or RequestBin to get a temporary public HTTPS URL.
• Access to the Automation section of your Feedspace workspace.
• At least one review form in Feedspace that you can submit a test review through.

Steps

Step 1: Get a Temporary Public URL

1. Open webhook.site in your browser. A unique HTTPS URL is generated for you automatically and displayed at the top of the page.
2. Copy that URL. You will use it as your webhook endpoint in the next step. Keep the webhook.site tab open so you can watch incoming requests arrive in real time.

Alternatively, create a bin at RequestBin and copy the endpoint URL from there. Both services work the same way for this purpose.

Step 2: Create a Webhook in Feedspace Using the Test URL

1. In your Feedspace dashboard, click Automation in the left sidebar.
2. Click the Webhook tab.
3. Click Create Webhook.
4. Paste the temporary URL from webhook.site into the Endpoint URL field.
5. Click Create Webhook to save.
6. Click Edit on the newly created webhook row to open the event panel.
7. Select the events you want to test, such as Text Review Received, Video Review Received, or Audio Review Received.
8. Click Update Events to save your selection.

Step 3: Trigger a Test Event

1. Open one of your Feedspace review forms in a browser and submit a test review that matches the event type you selected. For example, if you selected Text Review Received, fill out and submit a text review through the form.
2. Switch back to the webhook.site tab. Within a few seconds a new request should appear in the left-hand request list.

Step 4: Inspect the Payload

1. Click the incoming request in webhook.site to expand it.
2. Review the Headers tab to see the X-Feedspace-Signature header that Feedspace attaches to every delivery.
3. Review the Body tab to see the full JSON payload containing the review data.
4. Confirm the payload structure matches what your integration code expects. Check fields such as the review type, content, reviewer name, rating, and form identifier.

Step 5: Test Signature Verification

Feedspace signs every webhook delivery with an HMAC-SHA256 signature so your server can confirm the request is genuine. To test your verification code:

1. Copy the raw request body shown in webhook.site.
2. Copy the value of the X-Feedspace-Signature header from the same request.
3. Find your webhook secret: go to Automation in Feedspace, click the Webhook tab, and copy the secret shown in the webhook row.
4. Run your verification function locally, passing in the raw body, the signature header value, and your webhook secret. If your code produces a matching HMAC digest, the verification logic is working correctly.

For a full explanation of how the signature is computed and how to implement verification, see the Feedspace webhook signature verification guide.

Step 6: Switch to Your Production Endpoint

Once you have confirmed the payload structure and your signature verification code is working:

1. Go to Automation in Feedspace, click the Webhook tab, and click Edit on the test webhook.
2. Replace the webhook.site URL with your production endpoint URL.
3. Click Update to save. Feedspace will now send all future events to your real server.

If you prefer a clean setup, you can also delete the test webhook and create a new one pointing directly to your production URL.

Common Confusion

I submitted a review but nothing appeared in webhook.site

Check the following. First, confirm that the webhook is active, not deactivated, in the Feedspace Webhook tab. Second, confirm that you selected and saved at least one event by clicking Edit on the webhook row. Third, make sure the type of review you submitted matches a selected event. For example, if you only selected Text Review Received and you submitted a video review, no payload will be sent.

My signature verification is failing against the test payload

Make sure you are hashing the raw request body exactly as received, with no modifications, extra whitespace, or re-encoding. Also confirm you are using the webhook secret shown in the Feedspace Webhook tab for this specific webhook, not the API key or the Automation Secret Key, which are separate credentials.

Can I use a local development URL such as localhost?

No. Feedspace requires the endpoint URL to be publicly accessible over HTTPS. A localhost address or an HTTP-only URL will be rejected at creation time. Use a tool like ngrok to expose your local server with a temporary public HTTPS URL if you want to test against code running on your own machine.

What You Can Do Next

• Read the webhook signature verification guide to implement server-side security checks in your production code.
• Review the full webhook payload reference to understand every field Feedspace includes in a delivery.
• Delete the test webhook once your production endpoint is live to keep your webhook list tidy.