HTTP response inspection

Response inspection is an opt-in debugging aid. It captures a bounded snippet of the Destination's HTTP response for an attempt.

Enable it

Turn on Capture response body when creating or editing a Destination. It is off by default.

Enabling capture does not change delivery success or retry behavior.

What is captured

• a short snippet of the response body;
• the response content type;
• whether capture was available;
• when the captured snippet expires.

Capture is bounded. Large responses are not stored in full. Binary or unsupported content may not produce a text snippet. A body can be unavailable because capture was disabled, the response was empty, storage policy rejected it, or retention expired.

Retention

Captured responses expire. Once expired, the body is no longer available even though the attempt metadata remains.

Do not use response inspection as an audit archive. Store any response you need to retain in your own system, subject to your privacy and data-retention obligations.

Access

Only roles permitted to inspect Event payloads (Developer and above) can read captured responses. Viewers cannot read payloads or response snippets. A captured response may contain sensitive data from your Destination; treat it as production data.

Availability

A response may be captured, empty, unavailable, or expired. Do not assume capture implies a body is available. Handle an absent snippet as a normal case.

Security

Capture happens after the outbound request and never includes DeadHook signing secrets. It may include data your Destination returned, so avoid echoing secrets in error responses.