Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

HookTray review

Free#25 of 32 in Webhook Testing Software

A privacy-focused inspector for viewing webhook traffic without server-side payload storage by default.

6.0/10Editor score
HookTray6.0 Visit HookTray

Reviewed by iTechGuides Editors · Editorial team · Updated Nov 2026

HookTray is a local-first webhook inspector for developers debugging integrations during local or staging development. It generates temporary webhook URLs, streams incoming HTTP requests to a browser through Server-Sent Events, and presents methods, paths, query strings, headers, body previews, and timing. The web application can receive requests from Stripe, GitHub, Shopify, Slack, or any HTTP client. Its solo and small-team fit reflects a focused inspection workflow rather than a broad integration-testing suite.

Privacy-oriented architecture is the product’s clearest distinction. Captured request history is stored in the browser with IndexedDB, while the stateless relay avoids server-side payload persistence by default. Sensitive-header masking happens in the frontend, and rate limits apply to token creation and webhook receipt. Open MIT-licensed source enables self-hosting alongside the cloud deployment option, giving teams control over where the inspector runs. These features suit developers who need short-lived visibility into webhook behavior while keeping payload handling close to their own browser or infrastructure.

HookTray stays intentionally narrow. It does not provide payload replay, mock endpoints, or a forwarding tunnel, so teams that need repeatable fixtures, simulated receivers, or routing into local services should choose a tool built around those workflows instead. Accounts, billing, and server-side retention are also outside its scope, and the project is described as an early preview. Pick HookTray when temporary capture, live inspection, masking, and browser-local history are the priority; choose an alternative when a mature, end-to-end webhook test environment is required.

HookTray pros and cons

  • Where it wins
    • Temporary URLs stream requests to a browser in real time
    • Browser-local IndexedDB history limits default server-side payload retention
    • MIT-licensed source supports self-hosted deployment and customization
  • Where it doesn't
    • No payload replay for repeating captured requests
    • No mock endpoints or forwarding tunnel
    • Early-preview project with community and documentation support

HookTray fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update