Retrieve a webhook delivery
Private beta: request access to use webhooks.
Retrieve one delivery: its status and error, the event body and headers it carried, and a targets entry per subscriber with the run or session it started or why its filter skipped the event. When the delivery resumed waiting runs, one more entry summarizes them.
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_.
Response
Successful request
The delivery's id.
"whd_1234"
The endpoint the delivery arrived on, or null if it has since been removed.
pending is waiting to be routed (including after a retryable error), processing is being routed, succeeded reached at least one subscriber or waiting run with nothing failed, failed means a subscriber failed after its retries, filtered means no subscriber's filter took it, and unmatched means runs were waiting on the endpoint but none matched and no subscriber took it.
pending, processing, succeeded, failed, filtered, unmatched The provider's id for the delivery, such as a Stripe event id or GitHub's X-GitHub-Delivery header.
"evt_1PqR2s3T4u5V6w"
Whether the request carried an x-trigger-test header, as test sends from the dashboard do.
The key the delivery was deduplicated on.
The verified event body, capped in size.
The request headers, with credentials such as signatures removed.
A hash of the raw request body.
For a failed delivery, the error and the subscriber it came from.
For a filtered delivery, why no subscriber took it.
One entry per subscriber, plus a waiter entry when the delivery matched waiting runs.

