Integrations Workflow
Standard Credit Report Workflow
- Consumer applies for credit with your end-user customer
- Obtain OAuth 2.0 access token
- Construct CR request with consumer information
- POST request to Innovis API
- Receive response with credit report data
- CRITICAL: Store reportReferenceNumber and consumerId
- Parse and process credit report data
- Make lending decision
- Provide adverse action notice if required
SECONDUSE Workflow
- Consumer authorizes sharing report with additional lender
- Retrieve stored reportReferenceNumber and consumerId from original CR
- Obtain OAuth 2.0 access token (if needed)
- Construct SECONDUSE request with:
- New endUserCode (for the secondary lender)
- Stored reportReferenceNumber
- Stored consumerId
- Original inquiry date/time
- POST request to Innovis API
- Receive confirmation response
- Share original credit report with secondary lender
- Document SECONDUSE transaction for compliance
Error Handling Workflow
- Receive API response
- Check returnCode field
- If returnCode is "Error":
- Log error details
- Check errorMessage for specific issue
- Retry if appropriate (network errors)
- Contact Innovis support for persistent issues
- If returnCode is "Record":
- Proceed with normal processing
Best Practices
Data Storage:
- Always store reportReferenceNumber and consumerId from CR responses
- Link these values to your internal transaction/application ID
- Store original inquiry timestamp for SECONDUSE requests
- Maintain audit trail of all API requests and responses
Performance:
- Implement connection pooling for API calls
- Use appropriate timeouts (30-60 seconds recommended)
- Cache OAuth tokens until expiration
- Monitor API response times
Compliance:
- Verify permissible purpose before each request
- Provide adverse action notices when required
- Maintain proper documentation for regulatory audits
- Submit SECONDUSE for all report sharing scenarios
Updated 21 days ago