Government-source verification for mortgage & banking teams (866) 850-4506   ·   Customer Login

API

Bring verification inside your own systems.

Place orders, track status and retrieve completed transcripts and validation certificates programmatically — so verification starts when your workflow says so. When a loan reaches the right milestone, your system places the verification order automatically. Status comes back to the LOS, and completed records return to the file — without anyone opening another portal.

Automation

Verification triggered by your systems, not by a person.

For institutions that want an order placed the moment a file reaches a stage, and status back without anyone checking a portal.

Place orders programmatically

Submit a verification request with the borrower and authorization details from your own system, and receive an order number back immediately.

Poll for status, or receive it

Track a request from authorization check through IRS submission to delivery. Poll the order endpoint on your own schedule, or have status pushed to a callback URL as the order changes state — so your team sees progress inside the tools they already watch rather than in another portal.

Retrieve completed records

Collect finished transcripts and validation certificates securely and attach them to the loan file automatically.

Developer preview

What an order actually looks like.

A request goes out, an order number comes straight back, status advances as the request moves, and the record returns when it is ready. Field names below are illustrative — the current specification comes with your documentation.

verification order · lifecycle Sandbox
Request
POST /verificationloan_reference: "4839201"borrower:       "Michael Carter"product:        "wage_and_income"tax_years:      [2024, 2025]authorization:  "on_file"
Response
order_id:       "1187742"status:         "accepted"loan_reference: "4839201"
Status
RECEIVED VALIDATING SUBMITTED PROCESSING COMPLETE
Result
order_id:    "1187742"status:      "complete"documents:   [ transcript.pdf ]
Illustrative example. Field names and payloads follow the current API specification.

Status model

The states your system has to handle.

Every order moves through a defined sequence, and one branch that needs handling separately. Building against these means no surprises in production.

RECEIVED VALIDATING SUBMITTED PROCESSING COMPLETE
HELD FOR REVIEW A request moves to HELD FOR REVIEW instead of SUBMITTED when validation finds something that would cause a rejection. It stays there until the problem is resolved, so your system should treat it as a state that needs human attention rather than an error or a failure.

Available outputs

What comes back.

Confirm the current output set with your integration specialist — what is available can depend on the product ordered.

PDFThe official transcript or document, exactly as issued.
STATUS DATAOrder status and completion metadata for your own tracking.
VALIDATION CERTIFICATEThe SSA Match or No Match result for identity orders.
STRUCTURED DATANormalized transcript values, where available for the product ordered.
TLS 1.3 Scoped API credentials Credential revocation Audit logging IP allowlisting View Security →
Test environment available

Build against a controlled environment with your integration specialist before production credentials are activated, so nothing is exercised against live taxpayer data while you are still wiring things up.

How integration usually goes

Four steps, and a specialist on the call.

Our implementation does not end when we send you credentials. A named verification specialist works through the workflow with your technical team.

  1. CredentialsSecure credentials issued for your environment, with test access first.
  2. Build against testPlace sample orders and confirm your handling of every status your workflow will see.
  3. Review togetherWe walk through the integration with you before it touches production files.
  4. Go liveProduction credentials issued, with a named contact who knows your implementation.
API access is provisioned

Most integration friction comes from decisions made early: how authorizations reach us, how you want status surfaced, and what happens to a held file. A short conversation at the outset saves considerably more time than it costs. Request the current API documentation and we will arrange it.

What to plan for

Questions worth settling up front.

DecisionWhy it matters
How authorizations reach usUploaded with the order, or already on file under an existing authorization — this shapes the whole flow
Which transcript productsReturn transcript, Wage & Income, business returns, SSA verification, or a standard combination
How status is surfacedWhether your team watches status in your system or only sees completed records
Handling held requestsWhat your workflow does when a request is flagged for review rather than submitted
ReconciliationPassing your loan number through so invoices and exports line up with your accounting

Ready when you are

See the API against your workflow.

Request the current API documentation and test credentials, or schedule an integration review with a specialist.