End User View Shared Report
An end user (agent or organization) requests to view a consumer's report that was shared with them via Consent to Share Report. relay checks that the share exists, hasn't expired, and hasn't been revoked before returning the report — every outcome flows back through the same render path in your backend.
End User UXPartner Backendrelay API
Steps
- End user requests to view a consumer's report in your application.
- Gather the consumer (renter) ID and the end user (agent or organization) ID and make the API call.
- Call the fetch endpoint for the end-user type —
GET /api/experian/agents/{agentId}/renters/{renterId}orGET /api/experian/organizations/{organizationId}/renters/{renterId}. - relay validates the share — it must exist, be unexpired, and not be revoked — then fetches and returns the shared report. If any check fails, the response says which.
- Render the returned HTML report (or the response message when a check failed). Recommended: persist the request and response timestamps.
- Display the report and response message to the end user.
Related workflows
- Consent to Share Report — how the share is created
- Revoke Consent to Share Report — why a share may be revoked
- Consumer View Requested Report — the consumer-side equivalent