About Requex.me
We are building the internet's most reliable, fast, and secure webhook testing infrastructure — completely free for all developers.
Our Founding Story
Requex.me was born out of profound frustration. As backend engineers and API developers, we spent countless hours building event-driven architectures involving Stripe checkout sessions, GitHub repository events, and complex Shopify inventory syncs. We kept running into the same bottleneck: inspecting what external services were actually sending to our servers in real-time.
The tools available on the market were either heavily gated behind expensive paid tiers, required tedious account creations, or lacked the fundamental capabilities needed for modern web development—like modifying response status codes to test how platforms handled server failures, or inspecting headers with granular precision. Alternatively, using local tunneling solutions like Ngrok meant installing dependencies, exposing local ports, and configuring complex proxy setups just to see a single JSON payload.
We decided that developers deserved better. Testing webhooks should be frictionless. You should be able to open a browser tab, get an instant unique URL, point your provider at it, and immediately see the data flow in—all within seconds. That’s exactly what we built with Requex.me. By prioritizing developer experience and zero-friction onboarding, we’ve created a diagnostic hub that respects your time and accelerates your development cycle.
Specific Use Cases
Requex.me is designed to handle a multitude of development scenarios. Here are just a few ways developers integrate our platform into their daily workflows:
Payment Gateway Integration
When implementing Stripe, PayPal, or LemonSqueezy, you must ensure your application correctly handles events like `payment_intent.succeeded` or `invoice.payment_failed`. Requex.me allows you to capture these payloads during initial sandbox phases, enabling you to build precise TypeScript interfaces and validation logic before writing any server code.
CI/CD Pipeline Monitoring
DevOps engineers use our endpoints to listen to GitHub, GitLab, and Bitbucket repository events. Verify that push events, pull request creations, and deployment statuses are emitting the correct payloads with the right HTTP headers, ensuring your automated deployment scripts trigger flawlessly.
E-commerce Automation
Shopify and WooCommerce rely heavily on webhooks for inventory syncing, order fulfillment, and customer updates. Developers use Requex.me to inspect exactly what data is pushed during a cart abandonment event, ensuring their custom apps sync data accurately without losing crucial transaction details.
Testing Retry Logic (Simulated Failures)
A robust system must handle network failures gracefully. Using our advanced simulation features, you can configure your endpoint to return a `500 Internal Server Error` or a `429 Too Many Requests`. This allows you to verify if your provider honors exponential backoff and retry policies properly.
Infrastructure Transparency
At Requex, we believe that transparency is key to establishing trust with the developer community, particularly when handling network requests that may contain sensitive structural data. Our infrastructure is built to be resilient, fast, and secure by default.
The Frontend: We utilize Next.js and React deployed on a globally distributed edge network (Vercel). This ensures that the application UI loads in milliseconds regardless of where you are in the world. We rely on TailwindCSS for our design system, ensuring a lightweight CSS bundle and rapid rendering.
The Backend Processing: Our core API is powered by a high-performance NestJS (TypeScript) server running on scalable containerized infrastructure. When a webhook hits our endpoint, it is immediately parsed, sanitized, and broadcast via secure WebSockets (Socket.io) to the connected client. This sub-second latency ensures you see the request the absolute moment it arrives.
Data Lifecycle & Security: We employ strict data ephemeral policies. Webhook data is stored in a high-speed Redis cluster solely for the purpose of serving your active session. We do not persist payloads in a long-term database, and we implement automated TTL (Time-To-Live) expirations that purge all request data shortly after it is received. All traffic is TLS encrypted (HTTPS), and we strictly enforce CORS policies to prevent cross-site request forgery attacks.
Our Developer Promise
- ✓Zero FrictionNo accounts, no credit cards, no login walls. Generate a URL and test immediately.
- ✓Absolute PrivacyEphemeral data processing. We don't harvest, analyze, or sell your test payloads.
- ✓Uncapped LimitsWe don't throttle your debugging process with restrictive request caps or pagination blocks.
- ✓Continuous InnovationWe actively maintain our tool stack and frequently release features requested by the community.
Open Source Philosophy
The software development ecosystem thrives on open knowledge and shared tooling. While the core Requex.me infrastructure is currently managed as a hosted service to guarantee uptime and performance SLAs, we are fundamentally aligned with the open-source philosophy. We actively contribute bug reports back to our upstream dependencies and plan to open-source critical components of our architecture—including our SDKs and local CLI tunneling utilities—in the near future.
Get in Touch
We're building this platform together with the developer community. If you have feature requests, bug reports, or simply want to chat about API architecture, our inbox is always open.
[email protected]