3
2 Comments

Introducing cRequest โ€“ A HTTP Request Inspection Tool by Cronhooks

Hey folks ๐Ÿ‘‹

We just launched cRequest, a lightweight HTTP request inspection tool built by the team behind Cronhooks (our webhook scheduling platform). If youโ€™ve ever needed to test webhooks, inspect incoming HTTP requests, or debug integrations quickly โ€” this is for you.

๐Ÿ›  Why we built cRequest

At Cronhooks, webhooks are our bread and butter. But we constantly ran into this problem: testing incoming HTTP requests should be simple, fast, and reliable โ€” yet the existing tools were often too bloated, or didnโ€™t fit well with modern developer workflows.

So we built cRequest with a few key principles:

  • ๐Ÿงช Instantly generate a unique URL to capture HTTP requests

  • ๐Ÿ” View method, headers, query parameters, and body in real-time

  • โ™ป๏ธ Session-based โ€“ refresh-safe, but resets on tab close

  • โšก No login required, no fluff โ€“ just open and use

๐Ÿ’ก Use cases

  • Testing webhook payloads from 3rd party services (Stripe, GitHub, etc.)

  • Debugging client-side API calls during development

  • Teaching/learning how HTTP works (perfect for demos)

  • Logging and monitoring HTTP traffic during testing phases

๐ŸŒ Try it now

๐Ÿ‘‰ https://crequest.cronhooks.io

Weโ€™d love to hear what you think โ€” feedback, bugs, feature requests, or even just a shoutout. Weโ€™re just getting started with cRequest and already have some exciting updates on the roadmap (response customization, history, team sharing, etc.).

Thanks for checking it out!
โ€“ Cronhooks team

posted toAvatar for product cRequest
cRequest
  1. 1

    Nice execution on keeping this lightweight - the "no login, no fluff" approach is exactly right for debugging tools. You need to get in and get out fast.

    The webhook payload use case is a solid wedge. We've been working in an adjacent space (API observability for agents) and see the same pain pattern: devs just want to see what actually got sent without setting up elaborate logging infrastructure.

    Curious about your roadmap - how are you thinking about persistence vs ephemeral sessions? The session-based approach keeps it simple but some debugging workflows benefit from comparing requests over time.

    Keep shipping!

  2. 1

    I often need something like this. I usually just run a little mirror server. I will check it out next time I need it.