A soft pull API that prequalifies applicants inside your product.
Returns a full credit report and score with no impact to the applicant’s score. One consistent schema across all three bureaus, so your mapping logic never changes.
The soft pull is the easy part. The stack around it is not.
Most providers will sell you a soft pull endpoint. Then you discover the hard pull lives with a different vendor, on a different schema, under a different contract.
Add identity verification and fraud checks, and you are maintaining three integrations to make one decision.
Run soft inquiries for prequalification with no impact to the applicant’s score.
Escalate the same applicant to a hard pull on the same credentials when they formally apply.
Request identity, fraud, income, and public records data from the same integration.
Receive one consistent response format regardless of which bureau answered.
Choose your score model per request, from FICO and VantageScore families.
ONE VENDOR, EVERY STAGE
The soft pull is the start, not the whole thing.
Most teams stitch this together: a prescreen tool at the top, a soft pull provider in the middle, a separate bureau relationship for underwriting. CRS supplies all three.
All three run on the same credentials and the same API. No second vendor to contract, no second compliance relationship, and no reconciling formats between providers.
WHY CRS
Built to carry the whole decision, not one call.
Need to qualify before you pull anything?
OffersIQ returns an eligibility answer against your own rules using as little as a name and address, with no credit data exposed back to you. It sits one step ahead of the soft pull, and runs on the same integration.
Evaluate it before you talk to anyone.
Documentation, response schemas, and score model references are all public. Send them to your engineers today.
curl --location --request POST ‘https://api-sandbox.stitchcredit.com:443/ap
--header ‘Content-Type: application/json’ \
--header ‘Accept: *’ \
--header ‘Authorization: Bearer eyJhbGciOiJIUzUxMiJ9.eyJzdWIiOiJkNzdjOWYzNS0 --data-raw ‘{
“lastName”: “YCSWL”,
“middleName”: “”,
“firstName”: “ASAD”,
“state”: “CA”, "consumerIdentity": {
"dob": {
"day": "20",
"month": "02",
"year": "1982"
},
"name": [
{
"firstName": "ASAD",
Tell us what you are building.
We will map the right bureaus, score models, and inquiry types to your flow before you write a line of code.
FAQ
Can we see the docs before talking to sales?
Yes. Full API documentation is public and linked below. Nothing is gated behind a form.
Do we need to be a Credit Reporting Agency?
No. CRS is the licensed CRA. You are credentialed as an end user under a permissible purpose, and our team runs that process.
How long is integration realistically?
The code is the fast part. Bureau vetting usually sets the timeline, and most customers are live in roughly two weeks.
What does the response look like?
JSON, on a consistent schema across bureaus, based on the MISMO 3.4 standard. Raw attributes or banded values, depending on your workflow.
Can we choose which bureau answers?
Yes. Specify the bureau and score model per request, or let routing and fallback logic handle it.
What happens when we need a hard pull?
Change the inquiry type. Same credentials, same endpoint, same schema. No new vendor and no new contract.
Is there a sandbox?
Yes. You can validate response formats and build against them before going live.