Inside Hookdeck Inspect: see the request before trusting the event
A recent Product Hunt launch makes webhook capture inspectable while documenting the access, retention and signature boundaries.
Product Hunt's 3 November 2026 daily board placed Hookdeck Inspect ninth with 112 points when checked on 4 November. This dated launch signal is not adoption, reliability or a final lifetime total.
Documented components, not a complete production inventory.
- Inspect HTTP API
- Confirmed Source creation, separate ingest/read interfaces and captured request retrieval
- Source URLs
- Confirmed link-access model and source-specific signature boundaries
- Webhook sample library
- Confirmed representative synthetic payloads; samples are not authentic signed events
A recent launch with a bounded popularity signal
The checked Product Hunt board records Hookdeck Inspect at #9 with 112 points for 3 November 2026. FreeStack reviewed official product documentation and API contracts. We have not created an endpoint, sent a payload, tested signature verification or measured reliability. Hookdeck is an established provider; the dated launch is Inspect, not the founding of Hookdeck.
Confirmed components: separate ingestion and inspection
The public HTTP API documents Source creation, separate ingest and inspect URLs, captured headers and payloads, and an endpoint for retrieving requests. Reads can wait up to 25 seconds by default for a new request. This is a confirmed interface contract, not disclosure of the databases, cloud platform, queues or complete production architecture behind the service.
A lightweight test surface has an explicit boundary
Inspect has a free no-account route, three-day request retention and a fixed 90-day browser session. The UI shows the latest 250 requests; API pagination reaches older retained requests. Source creation and reads are rate limited separately, while ingestion has platform limits. The API is labelled early beta, so clients should expect contract changes and check the current version.
A Source URL is link access, not private authentication
The official documentation says anyone with a Source ID can send, read and manage its captured data, and warns against production traffic. Signature checking is source-specific: some integrations accept a signing secret, while the documented Stripe and Shopify Inspect setup does not verify signatures. A displayed request must not be presented as an authenticated business event merely because it arrived.
Samples make shape visible, not provenance
Hookdeck's webhook library provides representative payloads with synthetic identifiers and timestamps. The samples do not carry your signing secret, and browser requests cannot reproduce every provider header. FreeStack's editorial lesson is to separate event shape, sender verification and processing guarantees into different review questions. These are design lessons, not measured product outcomes.
A smaller achievable learning workflow
The linked FreeStack guide uses Inspect, Bruno, VS Code and Git to prepare one fictional payload, compare a capture with a field contract and document duplicate, malformed and ordering cases. This is an editorial learning kit, not Hookdeck's production stack. Save the kit first; consider a managed event pipeline only for a named gap such as authenticated production delivery, longer retention or governed retries.
Sources & further reading
Follow the source for current details. Product Hunt is used for discovery and launch history; technical claims use provider documentation or the project repository.