Buyer-Supplied Bureau Data

If your back-end already has borrower-authorized bureau data, you can pass it when starting or resuming a Hybrid Experience journey.

This is optional. Hybrid Experience works even 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 against the exact Hybrid journey being started

Do not send bureau data directly from a browser or mobile app. Send it only from your trusted back-end.

Request Shape

Add a top-level bureau object to the Hybrid journey start call.

POST /api/v1/hybrid/personal-loan/borrowers/{borrowerProviderID}/journey

1
{
2
  "personal": {
3
    "contactNumber": "9876543210"
4
  },
5
  "journey": {
6
    "endUse": "travel",
7
    "bureauConsent": true
8
  },
9
  "bureau": {
10
    "type": "EXPERIAN",
11
    "data": {
12
      "score": 742,
13
      "accounts": [
14
        {
15
          "id": "account-1",
16
          "status": "active"
17
        }
18
      ]
19
    }
20
  }
21
}

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 forwarded into the headless profiling request.

After the start call succeeds, continue the normal Hybrid flow: poll offers, handle Account Aggregator if required, and request the Hosted handoff URL once the borrower selects an offer.

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, then continue with the Integrations Guide.