Replay a webhook delivery
Private beta: request access to use webhooks.
Route a delivery’s stored event again as a new delivery. Without targetId every current subscriber is checked against its filter again. With targetId the event goes to that one subscriber, even if its filter skipped it. A replay never resumes waiting runs. Replays start real runs, so the key needs permission to trigger every task the replay runs, and to write sessions if it reaches an agent’s subscriber.
Authorizations
Use a named environment API key. It starts with tr_dev_sk_, tr_prod_sk_, tr_stg_sk_, etc.
Create a named API key in the API Keys section of your Trigger.dev project dashboard. Choose the narrowest access preset that supports your integration.
Our TypeScript SDK will default to using the value of the TRIGGER_SECRET_KEY environment variable if it is set. If you are using the SDK in a different environment, you can set the key using the configure function.
Path Parameters
The delivery's id, starts with whd_.
Query Parameters
The subscriber to replay to: a webhook() task's id, or agentId:eventId for an agent's chat.event or channel. Listed in the endpoint's subscribers.