Skip to content
PayloadPuffin.
Join the waitlist

Webhook didn't arrive

Your receiver has no webhook, but the sender says it sent one. Start with the sender's response, then follow the event to its deliveries. An accepted request and a delivered webhook are different steps.

No acceptance receipt

Check the response to POST /v1/events or to the source's URL. A 202 means PayloadPuffin stored the request. Another status explains why it didn't accept it; use the response code to choose the next action.

If the sender never received a response, acceptance is uncertain. If the original request included an idempotency key, reuse it when retrying to avoid creating a duplicate.

Accepted, but the event isn't visible

Copy eventId from the receipt and call Get an event with an API key for the same app. It needs events:read.

A newly accepted event can briefly return 404 while processing finishes. Retry after a few seconds. If it still isn't found, check the ID and app. An older event also returns 404 once retention removes it. See Read events.

Visible, but no deliveries

Open the event in the console's Events page. Its status tells you what to inspect:

StatusNext action
unbuiltRead unbuiltReason, fix the source's configuration or code, then rerun it. See Unbuilt events.
unmatchedCheck that the intended destination is enabled and that its event-type and channel filters match. See Destination filters.

Matching happens when the event is processed. Changing filters later doesn't add missing deliveries to an existing event.

A delivery exists, but hasn't arrived

Select the delivery under the event. Read its status and latest attempt:

StatusNext action
pendingCheck the destination's health and active delivery controls to see whether sending is waiting.
deliveringWait for the attempt in progress to finish, then read its outcome. See Delivery states.
retryingRead the latest attempt's outcome and fix what failed before nextAttemptAt. See Retries.
heldDecide whether the old event should still reach the receiver, then resend the delivery.
failedRead the last attempt, fix its cause, then resend if you still need it delivered.
deliveredCheck your receiver's logs using the delivery ID from webhook-id; PayloadPuffin received a 2xx. See What the destination receives.

A destination's health of suspended is separate from a delivery's status. Inspect its circuit or automatic pause before trying to resend. See Delivery controls.

An attempt failed

The attempt's statusCode, latencyMs and error explain whether the receiver answered, the connection failed, or PayloadPuffin couldn't prepare the request. Start with Read the outcome.

If your receiver rejects the signature, verify the raw body with the destination's signing secret before parsing it. Follow Verify signatures.

If the signature passes but the body has the wrong shape, inspect the request in the console's attempt detail and compare it with your receiver's expected format. A transform can change that body. See What the destination receives.