Use Cases & Examples

Stripe / PayPal / Mollie Webhooks

When integrating a payment provider, you need to know the exact format of their webhook payloads. Use the Webhook Tester to:

1. Create an endpoint and copy the URL.
2. Enter the URL in your payment provider's webhook settings.
3. Trigger a test payment or use the provider's "Send Test Webhook" button.
4. Inspect the received payload to understand the data structure.

Testing Error Handling

Set the response status code to 500 to test how your payment provider handles failed webhook deliveries. Most providers will retry with exponential backoff.

GitHub / GitLab / Bitbucket

Debug your CI/CD pipeline webhooks:

1. Create an endpoint and set it as the webhook URL in your repository settings.
2. Push a commit or create a pull request.
3. Inspect the webhook payload to see the exact commit data, branch info, and event metadata.

Verify Signatures

GitHub sends a X-Hub-Signature-256 header. You can inspect this header in the Webhook Tester to verify your signature validation logic is correct.

Third-Party API Callbacks

Many APIs use callbacks to notify you about asynchronous operations:

• Email delivery status — Postmark, SendGrid, Mailgun
• SMS delivery reports — Twilio, Vonage
• File processing — Upload services that notify on completion
• Monitoring alerts — Uptime checks, error tracking (Sentry, PagerDuty)

Simulating Slow Responses

Set the response delay to 5000ms and the status code to 504 to test how a third-party service handles timeouts. This is critical for building resilient integrations.

Testing Different Content Types

Some services accept different response formats. Use the Content-Type setting to test:

• application/json with {"status": "ok"}
• text/xml with <response><status>ok</status></response>
• text/plain with just OK