Set Up API Users in Encompass – Proof Help Center
The article guides Encompass administrators through creating an API user with specific permissions—including Read/Edit Loans, Edit Subordinate Loans, and Encompass LO Mobile Connect—to enable Proof's integration using provided API keys, and instructs notifying the Proof Solutions Engineer to complete the connection and receive necessary eClosing forms.
Audience: Organizations
Now that you've received your API keys from Proof and ICE Mortgage Technology, Encompass admins need to set up API users to allow Proof to connect to your Encompass environment. You are just a few steps away from getting Encompass connected to Proof.
Task
Create an API user in Encompass with the API keys provided by your Proof Solutions Engineer when setting up the Proof Encompass integration. See Connect Encompass to Proof for more details.
Required permissions
The API user you create will need the following permissions set either directly or via a Persona:
- 1.Read/Edit Loans and Edit Subordinate Loans.
- 2.Persona-based permissions must include Encompass LO Mobile Connect. For example, the Loan Officer Persona in Encompass has this permission by default, but your configuration may vary.
- 3.Some production loans may have additional visibility restrictions (e.g., employee loans). API users need full read/write access to all loans and closing documents for which Proof orders will be placed.
Credentials
- Your user ID can be anything you like — most clients label it Proof API User.
- The API Client ID will be supplied by ICE Mortgage Technology and the Proof team. Enter it in the API Client ID field.
- Once your API user is created, notify your Proof Solutions Engineer to enter your client credentials into Proof.
Once your client credentials are connected in Proof, notify your Proof Solutions Engineer. Proof will then provide you with your CDO and Proof eClosing form to install in your Encompass instance.
Summary Checklist
- API user must have Read/Edit Loans, Edit Subordinate Loans, and Encompass LO Mobile Connect permissions.
- API users need full read/write access to all loans and closing documents where Proof orders will be placed.
- After creating the API user, notify your Proof Solutions Engineer to enter your credentials into Proof.
Still unsure? Contact Proof Support for help.
Related
Encompass Integration Overview for Lenders
The Encompass integration with Proof enables lenders to seamlessly automate loan processing and closing document management by converting Encompass loans into Proof transactions, allowing order placement and updates via a custom form within Encompass, automatically pulling borrower data and documents through ICE Mortgage Technology's APIs, and ensuring eSigned documents are pushed back into Encompass for centralized tracking across various closing types including hybrid and online closings.
Connect Encompass to Proof – Proof Help Center
The document provides detailed guidance for organizations on setting up the Proof-Encompass integration for lenders, emphasizing collaboration between Encompass administrators and Proof Solutions Engineers, recommending use of a UAT instance for thorough testing (preferably by state and starting with top states), and outlining key configuration steps including providing Regression UID and Client IDs, obtaining API keys from ICE Mortgage Technology, and setting up API users to ensure a smooth onboarding and go-live process.
Encompass Integration Supported Features and Requirements
The Notarize with Proof Encompass integration supports hybrid, hybrid with eNote, and online closings via a custom form, requiring collaboration between Notarize with Proof and the lender to configure and test the integration in UAT and Production environments, adherence to specific validations such as properly formatted contact information, limited borrower and signer counts, unique signer emails, and use of original ICE Mortgage Technology documents ordered to the Encompass eFolder, with API keys provisioned by ICE Mortgage Transactions and thorough lender testing and training before going live.
Recall Orders from Encompass – Proof Help Center
To update a transaction already sent to signers, use the "Recall from Signers" button on the Proof eClosing form in Encompass to move the order to a recalled draft state in Proof, make necessary updates, then resend it via "Send to Signers" or "Send to Title," with the option for automatic sending if auto-send is enabled.
Complete a Hybrid with eNote Closing from Encompass – Proof Help Center
The Proof Help Center guide details the process for completing a hybrid loan closing with eNote from Encompass using eOriginal, highlighting current limitations (support only for eOriginal-generated eNotes, excluding DocMagic and Ginnie Mae notes), prerequisites such as successful onboarding and eVault configuration, and specific required Encompass fields (including loan details, property address, and ULDD data) that must be completed before placing an order through the Notarize with Proof eClosing form to generate and send the eNote for signing.
Document pushback options – Proof Help Center
The Proof Help Center explains how to configure document pushback settings in the Proof Lender Portal, allowing users to choose whether completed e-signed files return to Encompass as merged PDFs or separate attachments, specify their pushback location (File Manager, custom folder, or original eFolder), manage audit trail PDF pushback with necessary permissions, and handle wet-signed documents in hybrid transactions with options for title agents to upload merged packages.