Secondary Use Request and Response

SECONDUSE Product Overview

The SECONDUSE product is used when you share a previously-pulled credit report with a different end-user customer (financial institution). This is required for FCRA compliance when reselling reports. Key Differences from Standard Credit Reports:

Request: Uses stored values from the original Credit Report response
Response: Returns confirmation only (not a full credit report)
Purpose: Posts an inquiry to the consumer's credit file showing the secondary user

When to Use SECONDUSE

Use SECONDUSE when:

You pulled a credit report for End User A
You now need to share that same report with End User B
The consumer has authorized the secondary use
You have a permissible purpose for the secondary inquiry

Example Scenario:

You pull a CR for "ABC Mortgage Company"
Consumer shops their loan to "XYZ Bank"
You share the existing report with "XYZ Bank"
You submit a SECONDUSE request to post XYZ Bank's inquiry

Request Structure

Endpoint: POST /InnovisGateway/orest/grs_v001/request

Minimum Required Fields for SECONDUSE:

{
  "customerId": "string",
  "customerTraceNumber": "string",
  "endUserCode": "string",
  "endUser": "string",
  "productCode": "SECONDUSE",
  "permissiblePurposeCode": "string",
  "softwareProviderId": "string",
  "accessMethod": "ID",
  "originalInquiryDate": "YYYY-MM-DD HH:MM:SS",
  "reportReferenceNumber": "string",
  "applicants": [
    {
      "consumerId": "string"
    }
  ]
}

Field Definitions - SECONDUSE Request

Field Name	Type	Length	Required	Description
customerId	AN	16	Yes	Your House Number Customer ID
customerTraceNumber	AN	30	Yes	Your unique transaction identifier
endUserCode	AN	16	Yes*	End User Code for the secondary user (*required if endUser not provided)
endUser	AN	30	Yes*	End User customer name (*required if endUserCode not provided)
productCode	AN	10	Yes	Must be "SECONDUSE"
permissiblePurposeCode	AN	2	Yes	FCRA permissible purpose code for the secondary use
softwareProviderId	AN	4	Yes	Your software/company identifier
accessMethod	AN	2	Yes	Must be "ID"
originalInquiryDate	DateTime	20	Yes	The date and time that the secondary use event occurred. (YYYY-MM-DD HH:MM:SS format)
reportReferenceNumber	AN	30	Yes	The reportReferenceNumber from the original CR response
applicants[].consumerId	AN	16	Yes	The consumerId from the original CR response

Example SECONDUSE Request

{
  "customerId": "1234567890",
  "customerTraceNumber": "TXN-2026-0002-SU456",
  "endUserCode": "9876543210",
  "endUser": "XYZ Bank",
  "productCode": "SECONDUSE",
  "permissiblePurposeCode": "17",
  "softwareProviderId": "TEST",
  "accessMethod": "ID",
  "originalInquiryDate": "2026-02-18 14:30:05",
  "reportReferenceNumber": "INNV-2026-001234567",
  "applicants": [
    {
      "consumerId": "9876543210"
    }
  ]
}

Response Structure

SECONDUSE responses are confirmation-only and include:

returnCode: Status code indicating success or error
reportReferenceNumber: Reference number for this SECONDUSE transaction

Example SECONDUSE Response:

{
  "returnCode": "Record",
  "reportReferenceNumber": "INNV-2026-SU-789012"
}

Important Notes

accessMethod must always be "ID" for SECONDUSE requests
originalInquiryDate must not be in the future
originalInquiryDate should match the timestamp of the secondary use event
Store the SECONDUSE reportReferenceNumber for your records
Each SECONDUSE request posts a separate inquiry on the consumer's credit report