Webhook for the inquiry.redacted event. An Inquiry can be redacted directly (via the dashboard or API) or as part of cascading redaction triggered by an Account redaction or an automated retention policy.
A redacted Inquiry preserves its current status — which may be any value, including created, pending, or needs_review for inquiries redacted before finalization, in addition to the terminal states (approved, declined, completed, failed, expired). Operational timestamps (created-at, started-at, decisioned-at, etc.) are preserved. The distinguishing signal is redacted-at, which is non-null on this event. Do not detect redaction from status — there is no redacted enum value.
On the redacted payload, PII attributes are nulled out regardless of the redaction path: the deprecated top-level identity attributes (name-first, name-middle, name-last, address-*, birthdate, email-address, phone-number, identification-number, social-security-number) and the corresponding entries inside fields, plus note. tags is emptied via cascading on inquiry tags.
reference-id is null only when the parent Account is also redacted (the cascading case). On a direct Inquiry redaction that leaves the parent Account intact, reference-id can remain populated. For more info see Webhooks Overview.
Header. An HMAC that you should use to check that requests are authentic. Compare this value with your own digest, computed from the request body and your webhook secret. For more info see Webhook Best Practices.
Return a 2xx status code to indicate that the data was received successfully. Any other status will trigger retries. For more info see Retry Logic.