Error Handling and Troubleshooting

Return Codes

Return CodeDescriptionAction Required
RecordConsumer foundNone - process response normally
No RecordConsumer not foundReview consumer information for accuracy
SuppressFile suppressedConsumer's file is offline, see provided reason
ExemptConsumer foundNone - process response normally
ErrorError condition foundCheck request format and required fields

Common Error Scenarios

Authentication Errors:

  • Symptom: HTTP 401 Unauthorized
  • Causes: Expired OAuth token, invalid credentials, IP not allowlisted
  • Solution: Obtain new OAuth token, verify IP allowlisting, check credentials

Invalid Request Errors:

  • Symptom: returnCode ERROR or HTTP 400
  • Causes: Missing required fields, invalid field formats, incorrect data types
  • Solution: Validate all required fields, check date formats, verify SSN is 9 digits

Network Errors:

  • Symptom: Timeout or connection refused
  • Causes: Network connectivity, firewall blocking, service outage
  • Solution: Check network connectivity, verify firewall allows HTTPS to Innovis, contact support

Troubleshooting Checklist

Before contacting support, verify:

  • Using correct environment URL (UAT vs Production)
  • OAuth token is valid and not expired
  • Request originates from allow listed IP address
  • All required fields are present
  • Field formats match specifications exactly
  • SSN is 9 digits with no dashes
  • Dates are in correct format (YYYY-MM-DD)
  • For SECONDUSE: using values from actual CR response
  • For SECONDUSE: originalInquiryDate is not in the future
  • For SECONDUSE: accessMethod = "ID"

Logging Best Practices

What to Log:

  • Request timestamp
  • customerTraceNumber
  • OAuth token (last 4 characters only)
  • Request payload (sanitize SSN, full names)
  • Response returnCode
  • Response reportReferenceNumber
  • Any error messages
  • Response time

What NOT to Log:

  • Full OAuth tokens
  • Complete SSNs
  • Full consumer names in plain text
  • Complete credit report data