Your First Webhook
This guide walks you through a realistic webhook debugging workflow.
Scenario
You're building a payment integration and need to verify that a service is sending the right data to your endpoint.
Step 1: Create a Persistent Bin
Sign in with GitHub, then click "Create a Bin" from your dashboard. This creates a persistent bin that's saved to your account.
Give it a descriptive name like "Stripe Test" by clicking the bin name in the top bar.
Step 2: Copy the Webhook URL
Your bin URL looks like:
https://spidylabs.com/hook/stripe-test
Copy this URL — you'll paste it into your service's webhook settings.
Step 3: Configure Your Service
In your payment provider's dashboard, add the SpidyLabs URL as a webhook endpoint. For example, in Stripe:
- Go to Developers → Webhooks
- Click "Add endpoint"
- Paste your SpidyLabs bin URL
- Select the events you want to receive
Step 4: Trigger an Event
Perform an action in your service that triggers a webhook — for example, create a test payment.
Step 5: Inspect the Payload
Back in SpidyLabs, you'll see the request appear in real time. Click on it to inspect:
- Headers tab — Check for signature headers (like
Stripe-Signature) and content type. - Body tab — See the full JSON payload with syntax highlighting. SpidyLabs formats JSON, XML, and form-encoded bodies automatically.
- Query tab — View any query parameters appended to the URL.
Step 6: Iterate
As you trigger more events, each request appears in the list. Use the search bar to filter by method, path, or content. Use keyboard shortcuts (press ? to see them) for faster navigation.
Tips
- Use cURL export to copy any request as a cURL command — useful for replaying webhooks in your local dev environment.
- Enable auto-forward (Pro) to automatically send captured requests to your localhost.
- Use request diff (Pro) to compare two webhook payloads side by side.