Experian Connect API

Experian's Credit Sharing Platform REST API

A Modern RESTful API

The Experian Connect API combines the proven power of knowledged based authentication along with our patented credit sharing platform to enable developers to built world class Fair Credit Reporting Act (FCRA) compliant web applications.

JSON Responses

JSON is a lightweight serialization language that is compatible with many different languages.

Token Based Identities

Once authenticated, users are issued tokens which are passed to avoid storing sensitive information.

Resource Oriented Architecture

Ease of implementation, agility of the design, and the lightweight approach

Flexible Product Options

Ability to select product options per user to maximize revenue.

API Pricing Guide

All users must complete the authentication process to be issued a user token. Once authenticated a product option is selected for either a single share or multiple shares following the pricing structure below. The single share option is our most popular option however the multiple share option becomes more cost effective when a consumer would like to share with 6 or more end-users.

Authenticate a User

  • Fee is per inquiry
  • Valid for 365 days if active
  • Valid for 90 days if in-active
  • API endpoint /user

Single Share

Multi Share

  • Refer to Connect API  Reseller Pricing Addendum
  • Wondering were to start?

    Below is a basic outline that can help to fast track your development.

    1. Map out your data flow.

    Once you have familiarized yourself with the services you can begin to build the basic user flow. By creating two valid user token you can easily view and share reports accross users.

    2. Design the user experience.

    After the basic user flow is in place you will want to start accounting for authentication errors and exclusion scenarios. We have outlined common areas to account for you to get you started.

    3. Define user interactions.

    There are several no-fee services available to you to take advantage of. This will include viewing/sharing previously purchased reports, and checking the authentication status of an existing user token.