How to Migrate from Webhook.site to HookRay in 60 Seconds (2026 Guide)

If you're hitting Webhook.site's 50-request URL limit, refreshing the page every time a new event arrives, or searching through hundreds of payloads to find one specific request — this guide is for you.

This is a step-by-step migration from Webhook.site to HookRay. The actual switch takes about 60 seconds. The longer guide below is here in case you want to map every Webhook.site feature to its HookRay equivalent before you commit.

TL;DR: paste a HookRay URL where your Webhook.site URL used to be. Your existing testing flow keeps working. The free tier captures 100 requests per month with persistent URLs and replay built in. Get a free webhook URL →

Why developers migrate

The Webhook.site free tier hits limits fast in any non-trivial integration:

If your stack mostly involves capturing real webhook payloads, replaying them while you debug your handler, and searching through history when something breaks at 2am — HookRay is built for that. If your primary use case is mocking specific HTTP status codes, stick with Webhook.site for now and check back when our custom-response feature ships.

For a feature-by-feature comparison, see our Webhook.site vs HookRay deep dive.

The 60-second migration

Step 1: Open hookray.com/app in a new tab. A free webhook URL is generated immediately — no signup, no credit card. Looks like:

https://h.hookray.com/abc123

Step 2: Open the dashboard of the service that's currently sending webhooks (Stripe, GitHub, Shopify, etc.). Find the webhook configuration where you previously pasted your Webhook.site URL.

Step 3: Replace the Webhook.site URL with your HookRay URL. Save.

Step 4: Trigger a test event from the source service. The webhook arrives in your HookRay dashboard within 1-2 seconds — no refresh required.

That's it. Your migration is complete.

The rest of this guide covers the workflow improvements you should now be able to use.

Mapping Webhook.site features to HookRay

"View incoming requests"

Webhook.site: shows a list of captured requests. You click each one to see the payload. Page refresh required to see new requests.

HookRay: live-updating list. New requests appear automatically. The expanded view shows the full payload, headers, query params, and timing.

"Custom response"

Webhook.site: configure the status code, headers, and body that your URL returns to the caller.

HookRay: not yet supported (returning 200 OK by default). On the roadmap. If this is a blocker, keep using Webhook.site for the specific webhook tests that depend on it — the two tools coexist fine.

"Custom Actions" / Forwarding

Webhook.site: configure rules to forward, transform, or react to incoming requests.

HookRay: not supported. We focus on inspection + replay. If you need workflow automation, pair HookRay with Pipedream, Zapier, or n8n.

Premium / paid tier

Webhook.site Premium: $9/month for 100K requests/month, custom domains, encryption.

HookRay Pro: $9/month for 10K requests/month, 30-day history, search, and replay across services. Same price point — different feature emphasis. We're built for the workflow (testing → debugging → replay), not for high-volume production traffic.

For comparing all the leading options side by side, see our best webhook testing tools roundup.

Migration example: Stripe webhook

If you're testing a Stripe Checkout integration, here's the before/after:

# Before (Webhook.site)
# In your Stripe dashboard webhook config:
https://webhook.site/abcdef-1234-5678-9012-abcdef123456

# After (HookRay)
https://h.hookray.com/abc123

Trigger a checkout.session.completed event from Stripe Test Mode. The HookRay UI shows:

• The full Stripe event JSON in a syntax-highlighted view
• Smart parsing that highlights id, amount_total, customer_email at the top
• The signature header for verification testing
• A Replay button to re-send the captured webhook to your local handler (great for fixing a bug without re-triggering from Stripe)

For more on testing Stripe webhooks specifically, see our Stripe webhook best-practices guide and the Stripe service page.

Migration example: GitHub webhook

# Before (Webhook.site)
# In your GitHub repo Settings → Webhooks:
Payload URL: https://webhook.site/abcdef-1234

# After (HookRay)
Payload URL: https://h.hookray.com/abc123
Content type: application/json

GitHub sends push, pull_request, issues, and other events. HookRay captures all of them. The smart-parsing layer highlights action, pull_request.number, repository.full_name, etc. without making you scroll through 200 lines of JSON. See the GitHub webhook service page for a complete event reference.

Frequently asked questions

Can I use Webhook.site and HookRay side by side during the migration?

Yes — there's no exclusivity. Many developers test the migration on a low-stakes integration first (a side project or staging environment) and only switch their main testing workflow once they're satisfied. Both tools accept any payload, so there's no incompatibility.

Will my Webhook.site Pro subscription auto-cancel?

No — you have to cancel that yourself. Once you're confident the migration is complete, log in to webhook.site, go to Account → Billing, and cancel. Your subscription remains active until the next renewal.

Is HookRay self-hosted? Open source?

HookRay is a hosted service today. We don't currently offer a self-host option. The capture pipeline is built on Vercel + Supabase, so the infrastructure is conventional and there's no vendor lock-in for the data — you can export your captured requests at any time.

What happens to my captured Webhook.site requests?

They stay on Webhook.site. There's no automated import (the two services don't have a shared format). If you need a specific captured payload, copy it manually before switching off Webhook.site.

How does HookRay compare on price?

Both are $9/month for the entry-paid tier. Webhook.site Premium emphasizes high-volume production traffic (100K req/mo). HookRay Pro emphasizes the testing workflow (10K req/mo, 30-day history, replay, search). Pick based on what your work actually involves.

For a deeper comparison, see our Webhook.site vs HookRay feature breakdown.

What HookRay doesn't have yet

In the spirit of an honest migration guide:

• Custom response codes — not yet built. If your tests depend on returning specific HTTP statuses, this is the one feature where Webhook.site still wins
• Custom Actions / forwarding — not on our roadmap. Use a workflow tool (Pipedream, Zapier, n8n) for this
• Custom domains for webhook URLs — Webhook.site Premium offers custom domains; HookRay Pro does not

If any of these is a blocker, that's fair feedback — drop a note and we'll let you know when (or if) it ships.

What HookRay does that Webhook.site doesn't

• One-click webhook replay — re-send a captured payload to a different URL while you debug. The single biggest time-saver in webhook testing.
• Search and filter — find any past request by method, body content, status, or timestamp. Webhook.site requires scrolling.
• Smart payload parsers — Stripe / GitHub / Shopify / Slack and 50+ services get auto-highlighted key fields. No more reading 200-line JSON to find the customer email.
• Real-time updates without refresh — your dashboard updates as new requests arrive
• Persistent URLs without an account — anonymous URLs survive across sessions
• Smart-parsing API — programmatic access to the parsed events from your code

Closing notes

The migration is genuinely 60 seconds — we're not exaggerating. The friction is psychological more than technical: switching tools feels heavier than it is. The first 24 hours after switching is when you discover the new workflow improvements (replay, search, smart parsing) that you didn't know you were missing.

Try it on one webhook source first. If it doesn't click, you've lost 60 seconds. If it does, you've upgraded the part of your daily workflow you complained about most.

Start with a free HookRay URL → — no signup, no card, captures the first 100 webhooks per month free.

Related guides:

• Webhook.site vs HookRay — feature comparison
• Hookdeck vs HookRay — production vs testing
• Webhook.site alternatives — 6 tools compared
• The 7 best webhook testing tools (2026)
• Stripe webhook best practices
• Webhook.site custom response codes guide