Calls POST /api/v1/consent-validation directly against the PrivTrust API and shows the real request and response.
user_id a consent was created under -- it's whatever identifier the fiduciary app sent at consent time, not necessarily an email. For a Google-login-only app (e.g. /bank), that's the numeric Google account id, visible on that consent's row in the console's Activity page -- not the email. Then pick purposes and, optionally, data items to check./bank demo first.No purposes selected, and no purpose catalog is loaded -- this runs a bare notice-level check ("does any active consent exist at all?"), with no per-purpose detail at all. Click Load purposes from notice above (Data Fiduciary mode) to get the full breakdown instead.