FlurryPORT
Capture and replay webhooks to localhost
Last verified:
What is FlurryPORT?
FlurryPORT is a webhook capture, inspection, and replay platform designed for developers who need to debug and test webhook integrations. The tool acts as a capture proxy that sits between webhook providers (like OpenAI) and your actual endpoint, recording every delivery including headers, body, webhook-id, timestamp, and your endpoint's response before forwarding to your real handler.
Key features include full logging of every webhook attempt (including 72-hour retries and duplicate webhook-ids for deduplication), on-demand replay of any captured delivery against development or production environments, transformation capabilities to reshape payloads, transformation routing for directing events to different destinations, and project secrets management. The free tier includes one transformation and captures live for about an hour without requiring an account.
FlurryPORT is specifically built for developers building fulfillment systems on webhooks, those testing webhook handlers locally without deploying public servers, teams needing environment isolation for testing (since OpenAI's scoping is project-level only), and anyone who needs to see exactly what webhooks their endpoint receives to implement proper deduplication logic.
The tool addresses the gap where webhook providers don't offer native logging, letting you subscribe wide to events but never let raw provider events directly touch systems that spend money. You capture first, transform deliberately, and route narrowly.
FlurryPORT pricing
Pricing model: Freemium
Free tier: No account required, captures live for about an hour, includes one transformation. Paid tiers: Scale power features including transformations, transformation routing, and project secrets. These power features all start at one on the free tier and scale with your plan. Paid tiers available at flurryport.io/pricing.
FlurryPORT pros
- Free no-account version available at flurryport.dev
- Captures live webhook payloads for about an hour on free tier
- Records complete delivery info: headers, body, webhook-id, timestamp
- Logs all 72-hour retry attempts from providers
- Shows duplicate webhook-ids for deduplication testing
- Replay any captured delivery on demand against dev or prod
- Transformation included on free tier
- No installation required
- Acts as middleware between provider and your endpoint
- Supports transformation routing for multi-destination setups
- Project secrets management for authentication
- Environment isolation for testing (beyond provider's project-level scoping)
- Forward target configurable to your actual endpoint
- Full log of every attempt including failures
- Point-and-use: just paste endpoint in provider's webhook settings
FlurryPORT cons
- Free tier captures only live for about an hour
- No account required for free tier limits persistence
- Transformation routing starts at one on free tier
- Project secrets limited on free tier
- Paid tiers required for scaling power features
- Not native provider logging (requires proxy setup)
- Free tier only includes one transformation
- May add slight latency as middleware layer
Frequently asked questions about FlurryPORT
What is FlurryPORT?
FlurryPORT is a webhook capture, inspection, and replay platform. You point your webhook providers at the FlurryPORT capture URL and set the forward target to your actual endpoint. You get a full log of every attempt including retries and duplicate webhook-ids, and you can replay any captured delivery against dev or prod on demand.
Is there a free version?
Yes, there's a free no-account version at flurryport.dev. You can try it against a throwaway endpoint first without creating an account. The free tier includes one transformation and captures live for about an hour.
How do I set up FlurryPORT?
Point OpenAI's webhook (or any webhook provider) at the FlurryPORT capture URL and set the forward target to your actual endpoint. No installation required - just paste an endpoint from flurryport.dev into your provider's webhook settings.
What webhook information does FlurryPORT capture?
FlurryPORT captures every delivery exactly as sent: headers, body, webhook-id, timestamp, and your endpoint's response. It logs all 72-hour retry attempts and any duplicate webhook-ids so you can see exactly what to dedupe on.
Can I replay webhooks with FlurryPORT?
Yes, you can replay any captured delivery against development or production on demand. FlurryPORT replays a selected sequence in exact order, waiting for each request to complete and stopping at the first failure, providing end-to-end pipeline testing.
What is transformation routing?
Transformation routing lets you direct transformed events to different destinations. It's a power feature that starts at one on the free tier and scales with paid plans, allowing you to put one transformation between your events and anything that spends money.
Why do I need FlurryPORT instead of native logging?
Until webhook providers ship native logging, FlurryPORT provides the workaround of putting a capture proxy in front of your endpoint. It addresses the environment isolation gap since OpenAI's scoping is project-level only, letting you replay against different environments.
Do I need to install anything?
No, nothing to install. FlurryPORT is a no-account, no-installation service. Just paste an endpoint from flurryport.dev into your provider's webhook settings and it captures live for about an hour on the free tier.
What is the best practice for webhook fulfillment that FlurryPORT supports?
Subscribe wide, but never let raw provider events touch the system that spends money. Capture first with FlurryPORT, transform deliberately to reshape payloads, then route narrowly to your actual destinations. This prevents costly mistakes from unprocessed webhook events.
How does FlurryPORT help with deduplication?
FlurryPORT logs all duplicate webhook-ids that providers send, so you can see exactly what to dedupe on in your handler. You get a full log of every attempt including the 72-hour retries, making it clear which webhook-ids are duplicates that need handling.