Get bulk-delivery job status for loans
In: header
Path Parameters
Job ID returned by POST /v1/loans/bulk-delivery
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v1/loans/bulk-delivery/string"{
"bytes": 0,
"chargedCount": 0,
"completedAt": "string",
"creditLedgerId": "string",
"creditsCharged": 0,
"downloadUrl": "string",
"entityType": "string",
"error": "string",
"estimatedTotal": 0,
"format": "parquet",
"jobId": "string",
"processed": 0,
"resultsUrl": "string",
"startedAt": "string",
"status": "queued"
}{
"error": "string"
}{
"error": "string"
}{
"error": "string"
}Get loan by ID GET
Previous Page
Search individual loan records with filters POST
Search and list individual public-record mortgage and deed loan records — one row per loan (purchase, refinance, origination). Filter by geography (state, county, city, zip), lender, originator, loan amount, interest rate, loan type/purpose, and recording date, with sorting and cursor pagination. This is the discrete per-loan record search: use it to find specific loans or build a filtered loan list. Each row carries the property address, loan terms, the originating loan officer, and `borrowerStatus` — so this is also how you pull a loan officer's own funded production ("my closed loans", "my past clients", "my book of business"): filter by `originator` (their NMLS id), and add `borrowerStatus` for borrowers still in the home — that is the five current-owner codes (`Current`, `R_CWCLO`, `R_CWNLO`, `E_CWCLO`, `E_CWNLO`), NOT `"Current"` alone, which omits everyone who has since refinanced. That is market data, not CRM data — it does not require the loan officer to have added anything to a CRM workspace. (For aggregate market rates and volumes use the market search; for one loan by its ID use the loan detail endpoint.) If you only need how many loans match and not the records themselves, send the same request body to `countLoans`.