Integrations
Arive, DU and LP, UWM, Teams and your own systems through the API: what the page reads from each, what it writes, and the one click that stays with a person.
Updated 2026-09-26
Integrations
The page works through access you already hold, and your own systems can work a loan without it. Arive, DU and LP, UWM's portals, Teams and your own CRM sit around it as adapters, and one click stays with a person: the AUS run.
What it reads
| System | What the page reads | Through |
|---|---|---|
| Arive or EASE | The loan file: the application, the employers and their dates, the liabilities, the accounts, the property, the fees and the terms | The MISMO 3.4 export either already produces, added with the documents. Or the loan by its number from Arive, with your own keys |
| DU and LP | The findings report or feedback certificate: the recommendation, the ratios, loan amount, LTV, reserves, product, term, and every message with its identifier | Added as a file. Reports in their published layouts are read by code from the report's own text; a scan is read by the model |
| Income and asset documents | Paystubs, W-2s, 1099s, returns and schedules, K-1s, verifications, award letters, bank statements, the credit report | Added as files: PDFs, photos, TIFFs or a zip, each scanned for viruses before anything opens it |
| Microsoft Teams | Who is signed in | The tenant's own sign-on, in the same page as a Teams tab |
| Your own system | New loans with their files and answers, the option chosen, the AUS's next answer | The API, with a key one of your specialists issues |
What it writes
| System | What the page writes | Through |
|---|---|---|
| Your result store | Every result as a PDF with its evidence crops and citations; the chosen option as a MISMO 3.4 file | The Loan file drawer on the page, and the API |
| Arive | The result's reference, into the loan record | The adapter, with your keys |
| Microsoft Teams | A message into the channel when a result lands | A Workflows webhook your administrator configures in your tenant |
| Your own system | A signed notice at each milestone: income ready, an option ready, an answer needed, approved, no option left, the read stopped, closed | The webhook address named on the API key |
Your own system, through the API
A specialist makes a key in Admin, under API. The key acts for that person: the loans it starts are theirs and open in their page. It is shown once, and only its SHA-256 is kept; a lost key is revoked and replaced, and a revoked key stops at once. A key cannot manage keys or act with the specialist role.
The API at /api/v1 does what the page does: start a loan with its files and answers, read where it stands, answer what it asks, choose an option, send the AUS's next answer, fetch the result PDF and the MISMO 3.4 structure, and close the loan. Your install serves its description at /api/v1/openapi.json and a guide at /api/v1/docs.
A key can name a webhook, an https address. Each notice carries ids and links, never borrower data, and is signed with HMAC-SHA256 under a secret shown once with the key. A notice not answered with a 2xx within 15 seconds is tried again after 30 seconds, 2 minutes, 10 minutes, 1 hour and 6 hours. Its id is the same on every try, so a receiver keeps the ids it has handled.
The AUS run
The page returns an option as fields: each with its current value, its proposed value and the rule. Copy for EASE puts them on the clipboard; the loan officer enters them in EASE or Loan Lab, runs DU or LP, and adds the answer to the loan. The same option is a MISMO 3.4 file, which ChatUWM accepts for a One-Click AUS run and which Arive imports as a new loan.
UWM's terms
Until UWM's own overlay document is on file, UWM's public product-page terms are a labelled rule set with a retrieval date: minimum credit score, maximum LTV and DTI, reserves and product restrictions as printed. Where nothing on file covers a point, the result names the agency rule it ran.