---
title: "Soft Pull API for Prequalification | CreditPullEngine"
description: "Prequalify consumers without affecting their credit score. Form-encoded HTTPS POSTs, SMS consent for phone-number pulls, and a sandbox to build against first."
url: "https://creditpullengine.com/products/soft-pull-api"
---

Soft Pull API

# Prequalify with a few HTTPS calls.

Soft pulls let you prequalify a consumer without affecting their credit score. The API is form-encoded POSTs with an API key, so any stack that can send an HTTPS request can use it. Build in the sandbox, then switch the host to production.

  [Get Sandbox Access](/get-started/) [Read the API docs](https://docs.creditpullengine.com)

No SDK required. 1M+ API requests since 2024.

      Sample data

The endpoints

## Four calls cover the whole flow.

Every request is a form-encoded POST or a GET with your API key. The same paths work on the sandbox host and in production.

- POST /pull ### Pull with standard identifiers Send the consumer's identifying details and the pull runs. Use it when your intake already collects them.
- POST /phone/authorize ### Ask for consent by text Start a phone-number pull. The consumer receives a text asking them to consent and gets a one-time passcode to verify.
- POST /phone ### Complete the phone-number pull Once the consumer has consented and verified, complete the pull and receive the report ID.
- GET /getreport/{pdf|json|html}/{id} ### Fetch the report in the format you need Retrieve the same report as a PDF for the file, HTML for a screen or normalized JSON for your code. Full reference at docs.creditpullengine.com

Choosing a pull

## Phone-number pull or identifier pull.

Both return the same report. The difference is what you know about the consumer when the request starts.

    TopicPhone-number pullIdentifier pull What you sendThe consumer's phone numberStandard identifying detailsEndpointsPOST /phone/authorize, then POST /phonePOST /pullConsentThe consumer consents by textCollected in your own flow, with the locked FCRA authorizationVerificationOne-time passcode by textYour intake processBest forFirst calls where the consumer doesn't have every detail handyForms and CRMs that already capture identifiersReport formatsPDF, JSON, HTMLPDF, JSON, HTML

Endpoint details and required fields are in the reference at docs.creditpullengine.com.

Sandbox to production

## Build first, go live when you're approved.

Request sandbox credentials as soon as onboarding starts. Approval typically takes about two weeks, and you can build the whole integration in the meantime.

1. 01 ### Get sandbox credentials. Point your requests at sandbox.creditpullengine.com and pull fictional sample consumers. Get Sandbox Access
2. 02 ### Build against the docs. Wire up consent, the pull and report retrieval. Our engineers help map the response to your CRM. Read the API docs
3. 03 ### Switch to production. Once your company and office are verified, you get production credentials. Change the host and key, keep the code. Talk to an engineer

For developers

## What to expect, plainly.

There is no SDK to install and no client library to keep current. If your stack can send an HTTPS POST, it can pull a report. That covers a backend service, a CRM workflow or a script.

Consent is part of the API, not something bolted on. FCRA authorization blocks can't be edited or removed, phone-number pulls verify the consumer with a one-time passcode, and every pull is logged in the audit trail. Your company certifies a permissible purpose before any report.

Not sure whether a soft pull fits your use case? Our guide explains the difference between soft and hard pulls, and we're happy to talk through which pull types your workflow needs.

- Form-encoded POSTs authenticated with an API key.
- Sandbox and production share the same paths.
- Normalized JSON responses across every report.
- Repeat pulls of the same consumer within 24 hours return the cached report.

## Questions developers ask.

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

No. Soft pulls used for prequalification don't affect the consumer's score. Our guide on soft pulls vs hard pulls explains the difference.

  Is there an SDK?

No SDK is required. The API takes form-encoded HTTPS POSTs with an API key, so any language or platform that can make an HTTPS request works.

  How does consent work for phone-number pulls?

POST /phone/authorize sends the consumer a text asking for consent, and they verify with a one-time passcode. POST /phone completes the pull once they have.

  Can I build before I'm approved?

Yes. Request sandbox credentials as soon as onboarding starts and build against sandbox.creditpullengine.com. Production access follows approval.

  Which formats can I retrieve?

PDF, JSON and HTML, through GET /getreport/{format}/{id}. The JSON is normalized across reports.

## Related

- Guide ### Soft pull vs hard pull What each pull is, and when a soft pull is enough.
- Solution ### Developers How engineering teams integrate CreditPullEngine.
- Solution ### Startups Prequalification for fintech builders, pay for what you pull.

## Make your first sandbox pull.

Request sandbox credentials and build against the same endpoints you'll use in production. Our engineers are a message away.

  [Get Sandbox Access](/get-started/) [Book a Live Demo](/contact/)