The mortgage file,
answered by API
Payoff figures, lien status, eNote control and note fields, as typed records with the issuer named and the loan record cited.
Three surfaces, one loan
Each returns a typed record, never a lead form.
Payoff and lien
Payoff, per diem and good-through date, with lien and release status.
eNote and eVault
Who controls the note, where it sits, and every transfer.
Document intelligence
The note and disclosures, read into fields that cite their page.
The boundary starts at the URL
Mortgage has its own regime, so this door stands as its own entity.
- The decision
Lender-reserved acts stay with the lender
Extending credit, taking the application, negotiating terms and deciding; this door returns the record.
- The source
Every record names its source
The issuer is named on it and the loan record it came from is cited.
- The key
The family key opens it
The key that opens apis.finance, apis.credit and apis.loans opens this door too.
Who carries the file
Built for the people a payoff, a lien or an eNote waits on.
- eVault engineering
Owns an eVault integration that needs control state.
- Founders
Ships a product that waits on payoffs quoted by phone.
- Servicing operations
Owns payoff and lien release against a statutory window.
- Platform product
Needs a mortgage data partner behind the platform.
One key, every door
This door answers for itself, on the family key.
Request access
Tell us what you’d build, which surface first and the volume you expect.
Received.
We’ll reply by email.