Buyer-Supplied Bureau Data
Buyer-Supplied Bureau Data
If your back-end already has borrower-authorized bureau data, you can pass it into supported Aarthik Labs journeys.
This is optional. Hosted and Hybrid journeys can still work when you do not send bureau data.
When To Use This
Use buyer-supplied bureau data when:
- your application has already received a bureau report for the borrower
- the borrower has authorized your application to share that report with Aarthik Labs
- you want Aarthik Labs to store the report with borrower and journey context
Do not send bureau data directly from a browser or mobile app. Send it only from your trusted back-end.
Where This Applies
Hosted Experience Shape
For Hosted Experience, add a top-level bureau object when creating the Hosted Experience URL.
Hybrid Experience Shape
For supported Hybrid journeys, add a top-level bureau object to the journey start or resume call.
Required Fields
Optional References
You may also send:
These fields are optional. If you do not have them, omit them.
What Happens Next
Aarthik Labs stores the raw bureau data with borrower, tenant, application, and journey context. The raw report is redacted from audit payloads and is not exposed to borrower-facing Hosted screens.
The API still returns the normal journey response for the experience you are using. The bureau object is not returned in the response.
Note: Buyer-supplied bureau data is stored safely for audit, provenance, and supported processing. Do not assume it will automatically replace all lender or bureau pulls unless Aarthik Labs has confirmed support for your bureau format.
Read the exact request contract in the API Reference.