Integrations
Encompass, Arive, DU and LP, the documents borrowers send, Teams and your own systems through the API: what Proxara reads from each and what it writes.
Updated 2026-10-18
Integrations
Proxara works inside the loan origination system your officers already use, Encompass or Arive, through access your shop already holds, and runs DU and LP through that same access. A Proxara mailbox, a texting number, Microsoft Teams and your own CRM are optional.
Encompass
Proxara works inside your Encompass as your own integration, with an API key your Encompass administrator issues and a user of your instance that Proxara signs in as for the work nobody is watching. Whatever an officer does inside a loan runs as that officer, with their own Encompass rights.
| What | How |
|---|---|
| New loans | Encompass tells Proxara when a loan is created or saved and when a document is filed. Proxara starts each new loan by itself, as the loan officer Encompass names on it. |
| The loan and its documents | The loan's own MISMO 3.4 export, and every file in its eFolder |
| What Proxara writes | Each job's documented income and each account's balance into the application, the chosen change into the loan's fields, and the result PDF into the eFolder. A figure someone typed after Proxara wrote it stands until the officer decides. |
| DU and LP | Ordered through Encompass on your own DU or LPA credentials. The findings land in the eFolder, and Proxara reads them from there. |
| Decisions | Encompass tasks for the loan's officer, under a task template named Proxara. Each task opens straight to Proxara. |
| Where each loan stands | A custom field, CX.PROXARA, that officers add to their pipeline view: "2 decisions", "Ready for DU", "Waiting on DU" |
| Proxara's screen | A Custom Tool inside the loan, signed in with the officer's own Encompass sign-in, which Proxara checks with ICE |
Deployment lists the four things your Encompass administrator sets up.
Arive
With your company's three Arive keys (the client ID, the secret and the API key), Proxara picks up each new loan when Arive creates it, reads the loan and its documents by the loan's number, and writes its work back into the loan. DU and LP run through your lender's portal, with your credentials. A loan can also start from Arive's MISMO 3.4 export, added on Proxara's screen.
Documents from anywhere
- The loan itself: the eFolder in Encompass, and the loan's documents in Arive.
- The borrower's page. Proxara texts or emails the borrower, in the loan officer's name, for what the loan still needs, with a link to a page on their phone. What they send there joins the loan once it is checked.
- A Proxara mailbox, optional. Officers forward anything to it, such as a corrected paystub a borrower sent to the wrong address, and borrowers may email it too. Proxara puts each attachment on its loan by the sender and the names it gives, or holds it for the officer to place. Exchange lets Proxara reach this one mailbox and no other.
- A texting number, optional, through your own Twilio account. Borrowers text photos of their documents to it.
- By hand, on Proxara's screen.
Every file is scanned for viruses before anything opens it, whichever way it came.
Microsoft Teams
A message into a channel when a result lands, through a Workflows webhook your administrator configures in your tenant. It is off until you set it up, and its address stays in your Key Vault.
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 on their screen. 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 Proxara's screen 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, for a signed notice at each milestone: income ready, an option ready, an answer needed, approved, no option left, the read stopped, closed. 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.
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.