Gareth Wilson

Replaying requests, multiple API keys, and wildcard topic routing - Hookdeck July 2026

Published Aug 6, 2026

July's releases include replay, support for multiple API keys, and seven new verified sources in Event Gateway, plus wildcard topic routing for Outpost and a CLI release.

Replay Any Request

Add a connection to an existing source and it starts empty. The traffic that arrived yesterday belongs to the connections that existed yesterday, and the only way to get it into the new one has been to ask the provider to resend — if they even support that.

Replay closes that gap. Hookdeck re-ingests the original request through the full pipeline as if it had just arrived, creating a new request and one new event for each target connection. The original is left untouched.

By default a replay targets every active connection on the request's source, including connections added after the original request arrived — which is what makes backfilling work. You can also target a specific set of connections, or a different source entirely. When the targets span multiple sources, the replay fans out into one new request per source.

Because the replay runs through your current configuration, your filters, transformations, and deduplication rules are all re-evaluated. That's what makes replay useful after fixing a transformation — and it also means a replayed request can be filtered or deduplicated out, exactly as a newly-arrived one can. Deduplication is worth watching in particular: a replay reproduces the original payload exactly, so replaying within a connection's deduplication window is dropped as a duplicate of the original.

You can replay a single request from the Requests view, or replay the request behind an event from the Events view. To reprocess a whole time window at once, bulk replay takes a filtered set of requests and replays them onto a target source, resolving that source's active connections as it runs. Both are also available in the API, via POST /requests/{id}/replay and POST /bulk/requests/replay.

Replay vs. Retry

Replay and retry sound similar, but they operate on different entities, and that's the whole distinction: a retry re-runs an existing entity, a replay creates a new one.

Retrying an event adds a new delivery attempt to that same event and sends it to the same destination — automatically after a failed delivery, or manually when you trigger it.
Retrying a request re-runs the event-creation logic on that same request, and only ever on the request's own source.
Replaying a request creates a new request, and new events that can be routed to any connection in the project — including ones on a different source, and ones that didn't exist when the original arrived.

So you retry when delivery failed and you want the same thing sent again; you replay when you want the request reprocessed under your current rules or routed somewhere new.

Each replay creates a new request and new events, so replays count toward usage the same way newly-received traffic does.

Multiple API Key Support

We now support multiple API keys per project, allowing you to manage and rotate keys for better security practices. Previously, each project had only a single API key, and to get a new one you had to roll the current key and replace it. Now you can create many, and name, filter, and rotate them individually, too. Every key has the same full access — there's no read-only or scoped key. Available now on the API Keys & Secrets page under Settings in your dashboard.

Outpost v1.0.7 & v1.1.0

Outpost v1.0.7, adds routing improvements that changes how destinations subscribe to topics.

Previously, destinations could match exact topics or use * to catch everything. v1.0.7 adds wildcard pattern matching: user.*, *.created, order.*.completed. This makes it practical to subscribe to entire topic families without listing each variant, useful when topics include dynamic segments like resource IDs or lifecycle stages.

Thanks to first-time contributor @Abdulmumin1 for implementing wildcard topic subscriptions. We also fixed up a few bugs - see the full release notes for details.

Outpost v1.1.0 also landed in July, adding configurable system header names. Outpost injects system headers (event-id, timestamp, topic, signature) into delivered webhooks. You can now set the exact name for each via environment variables:

DESTINATIONS_WEBHOOK_EVENT_ID_HEADER_NAME=x-my-event-id
DESTINATIONS_WEBHOOK_TIMESTAMP_HEADER_NAME=x-my-timestamp
DESTINATIONS_WEBHOOK_TOPIC_HEADER_NAME=x-my-topic
DESTINATIONS_WEBHOOK_SIGNATURE_HEADER_NAME=x-my-signature

The previous DESTINATIONS_WEBHOOK_DISABLE_DEFAULT_*_HEADER flags are deprecated.

We also added IAM role authentication for AWS SQS, new operator events, and dead-lettering for stuck retry tasks, among other improvements.

Thanks to @ambroziepaval, @mvanhorn, and @LendritIbrahimi for their contributions.

Read the v1.1.0 release notes and upgrade guide before upgrading.

CLI v2.3.1

CLI v2.3.1 shipped adding payload copying and full MCP filter parity.

Three keyboard shortcuts now handle payload copying in the event details view:

C — copy the complete request (request line, headers, and body)
H — copy just the request headers
B — copy just the request body

Off-screen content is included, so the full payload copies regardless of terminal size. Works natively on macOS and Windows. Linux and BSD users need xclip or xsel.

The Event Gateway MCP server's hookdeck_events and hookdeck_requests list tools now support the full API filter set:

Payload search: body, headers, parsed_query, path
Date windows with ISO 8601: created_after, last_attempt_after, ingested_after, and _before counterparts
Events: id, attempts, cli_id, successful_after/before, last_attempt_after/before
Requests: id, created_after/before, ingested_after/before, order_by, dir

CLI also now supports authenticating listen without a prior login. hookdeck listen accepts --cli-key <user-scoped CLI key> or --api-key <project key> to authenticate a single run, useful in CI environments where running hookdeck login interactively isn't an option.

Update via npm install -g hookdeck-cli@2.3.1 or install via Homebrew, Scoop, or Docker.

Seven New Verified Sources

Event Gateway's source catalog grew by seven this month: Cloudinary, Volume, Statsig, Vapi, Attentive, Bunny Stream, and Tikkie. Browse all verified sources in the Hookdeck dashboard when creating a new source.