Skip to the operations

Credit Bureaus

Experian in a decision flow.

1 Experian operation a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.

Category
Credit Bureaus
Type
Credit Bureau
Authentication
OAuth 2.0 client credentials
Test environment
Separate sandbox host

Who they are

One of the three nationwide US consumer credit bureaus.

Experian collects consumer credit histories from lenders and furnishes them back as credit files and scores, under the reporting and dispute rules those files carry. Alongside the bureau it sells decisioning, analytics and identity products. Access is granted per contract — there is no self-serve key for a credit file.

What a flow can call

1 operation, each one a step you can place on the canvas.

  1. POST/consumerservices/credit-profile/v2/credit-report

    Consumer credit profile

    Pulls a consumer credit report.

Where it sits in the decision

Credit Bureaus calls have a natural place in a flow.

A bureau pull is the expensive call in a credit decision, so it belongs after the cheap eligibility rules that might make it unnecessary and before the scorecard that consumes it. What came back is kept with the decision: months later an adverse-action notice has to cite the file as it read at the time, not as the bureau would answer today.

Whatever Experian returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add Experian as a connection authenticating with OAuth 2.0 client credentials.
  • 02Experian runs a separate sandbox host, so a Sandbox flow can exercise the real call without touching production.
  • 03Place a Connection node and pick an operation — “Consumer credit profile” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using Experian in a flow.

How do I connect Experian to a decision flow?

Add Experian as a connection in your workspace authenticating with OAuth 2.0 client credentials, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Experian in a decision without ever seeing the secret.

Can I test Experian without touching production?

Yes. Experian runs a separate sandbox host, so a flow executing in Sandbox can make the real call against test credentials and you can read the actual response shape in the trace before anything reaches a customer. The flow does not change when it graduates — only which credentials answer.

What can a flow call on Experian?

1 operation: “Consumer credit profile”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Consumer credit profile”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Where in a decision should Experian be called?

A bureau pull is the expensive call in a credit decision, so it belongs after the cheap eligibility rules that might make it unnecessary and before the scorecard that consumes it. What came back is kept with the decision: months later an adverse-action notice has to cite the file as it read at the time, not as the bureau would answer today.

Also in Credit Bureaus

Ready when you are

Wire Experian into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs