Soft pull credit API for real-time prequalification

The CRS soft pull credit API returns a full-file credit report through a soft inquiry.

Lenders and marketplaces use it to show applicants the terms they may qualify for before a formal application.

The pull does not affect the consumer’s credit score.

Inquiry type

POST /credit-report
{
  "product": "prequalification",
  "inquiry_type": "soft",
  "bureaus": ["equifax"],
  "applicant": { "first_name": "Jordan", "last_name": "Avery", ... }
}

Credit score impactNone

Visible to other lendersNo

Typical usePrequalification and offer matching

Same schema. Same integration. One field changes.Illustrative request.

At a glance

Last updated: October 2026

Inquiry type: Soft. Switch to hard with one flag in the same schema.

Score impact: None for the consumer.

Data returned: Full Equifax File One tradeline section, inquiries, and public-record alerts.

Scores: FICO or VantageScore, optional.

Bureaus: One, two, or three bureaus, set with a single flag.

Response time: Under 2 seconds for a single-bureau pull.

Delivery: API, SFTP batch, or MISMO feed.

Required inputs: First name, last name, full 9-digit SSN, and current U.S. address. Middle name, suffix, and date of birth are optional.

Uptime: 99.9%

Security: SOC 2 Type II Certified

How it works

How a soft pull works

The applicant opts in
They submit basic details and consent to a soft credit check.
CRS runs a soft inquiry
CRS pulls the file through a soft inquiry. The consumer’s score is not affected.
You get the full file
The response returns tradelines, inquiries, public-record alerts, and an optional score.
Escalate when they apply
Send the same request with the inquiry flag set to hard. No second integration.

Options

Two ways to prequalify applicants

Both run through the same CRS API.

Soft pull prequalification

Prequalification Credit Report. A soft-inquiry, full Equifax file with an optional score. Requires the applicant’s SSN.

Prescreen offer matching

OffersIQ matches consumers to eligible offers from name and address. It runs as a prescreen, not a soft pull. Learn more

Why CRS

Why teams prequalify with CRS

One schema for soft and hard

Prequalify and underwrite through the same integration. Escalating is a flag change, not a second build.

Three bureaus, one integration

Pull one, two, or three bureaus. If your primary bureau is down, switch to another without new code.

Built for production

99.9% uptime, SOC 2 Type II certification, and US-based support.

Use cases

Where soft pulls fit

Personal loan lenders

Show real rate ranges before the application. Convert to a hard pull only when the applicant accepts.

Auto dealers

Prequalify buyers before they visit, then structure deals on known credit tiers.

Mortgage brokers

Check borrower eligibility early without a hard inquiry on the file.

BNPL and fintech

Decide at checkout or onboarding, and save the hard pull for later.

Compliance

Soft pulls still need a permissible purpose

A soft inquiry protects the consumer’s score. It does not remove your obligations.

CRS confirms your permissible purpose for each product during onboarding, before production access.

Prequalification and prescreening are different motions with different rules.

Developers

For developers

Soft and hard pulls share one endpoint and one response schema.

Responses arrive in CRS Standard Format, so every bureau reads the same way.

Start in the docs, then test against your own decision logic.

API documentation CRS Standard Format

What the response includes

Tradelines
Inquiries
Public-record alerts
FICO or VantageScore, when requested

FAQ

Questions about soft pulls

What is a soft pull credit API?

A soft pull credit API returns a consumer’s credit report through a soft inquiry. Lenders use it to prequalify applicants and match offers before a formal application. The CRS version returns a full-file report. It switches to a hard pull with one flag in the same schema.

Does a soft pull affect the consumer’s credit score?

No. A soft inquiry does not affect the consumer’s credit score. That makes it safe to run early in a funnel and as often as your use case allows. A hard inquiry, used for formal credit decisions, can lower the score and is visible to other lenders.

What data does the CRS soft pull return?

The response returns the full Equifax File One tradeline section, inquiries, and public-record alerts. A FICO or VantageScore is optional. Responses arrive in CRS Standard Format, so every bureau reads the same way.

What do I need to send with a CRS soft pull request?

Send the applicant’s first name, last name, full 9-digit SSN, and current U.S. address. Middle name, suffix, and date of birth are optional. The applicant submits these details and consents to a soft credit check.

Can I pull more than one bureau with CRS?

Yes. Pull one, two, or three bureaus, set with a single flag. If your primary bureau is down, switch to another without new code.

How do I move from a soft pull to a hard pull with CRS?

Send the same request with the inquiry flag set to hard. Soft and hard pulls share one endpoint and one response schema. Escalating is a flag change, not a second build.

When should I use OffersIQ instead of a soft pull?

Use OffersIQ to match consumers to eligible offers from name and address alone. It runs as a prescreen, not a soft pull. Use the soft pull when you need a full-file credit report. Both run through the same CRS API.

How fast is a CRS soft pull?

A single-bureau soft pull returns in under 2 seconds. Delivery options include API, SFTP batch, and MISMO feed. CRS maintains 99.9% uptime. If your primary bureau is unavailable, one integration lets you switch to another bureau without new code. Ask our team about timing for multi-bureau files.

Prequalify without the score impact

See how a soft pull fits your application flow.

Book a demo