The Ultimate Guide to Connecting Encompass with Microsoft Dynamics for Seamless Workflow
The loan origination software market hit $6.58 billion in 2025 and is projected to reach $7.35 billion in 2026. That growth is driven by one thing:...
Information Security Compliance
Add security and compliance to Microsoft 365
BI Reporting Dashboards
Realtime pipeline insights to grow and refine your learning operation
Integrations for Banks & Credit Unions
Connect LOS, core platforms, and servicing system
Productivity Applications
Deploy customized desktop layouts for maximum efficiency
Server Hosting in Microsoft Azure
Protect your client and company data with BankGrade Security
5 min read
Justin Kirsch : Jul 28, 2025 2:00:00 PM
ICE Mortgage Technology released three major Encompass Developer Connect updates in 2025 alone. The November 25.3 Service Pack shipped webhook notification improvements. The August 25.3 release added new REST endpoints. And the May 25.2 release expanded partner API coverage. If your team is still running legacy SDK integrations, the October 2025 deprecation deadline has passed.
Encompass API integrations connect your loan origination system to CRMs, compliance engines, document platforms, and borrower-facing tools through REST endpoints. They replace manual data transfers with real-time automation. For mortgage companies processing hundreds of loans per month, every manual handoff is a bottleneck worth eliminating.
This guide covers what Encompass APIs do, how they connect to the systems mortgage teams depend on, and what changed in 2025 and 2026 that affects your integration strategy.
Encompass APIs follow a RESTful architecture. They use standard HTTP methods and return data in JSON format. Every integration authenticates through OAuth 2.0 tokens tied to your Encompass Client ID.
Three components make the system work:
Authentication requires an API key linked to a specific Encompass instance. Each API user needs explicit permissions configured in the Encompass admin console. Rate limiting applies across all endpoints, so high-volume operations need batching strategies.
Not every integration works the same way. The right approach depends on who built it, where the data goes, and how it needs to flow.
Vendors like Stavvy, ValueLink, and Clear Capital build integrations through Partner Connect. These show up in the Encompass marketplace and connect through standardized API contracts. Clear Capital expanded its Automated Service Ordering (ASO) in early 2026, automating appraisal workflows directly inside Encompass.
Your internal team or MSP builds these. Developer Connect gives access to loan-level data, borrower records, pipeline queries, and document management APIs. This is the path for connecting Encompass to your own reporting dashboards, custom compliance checks, or internal workflow tools.
Encompass APIs are cloud-native by design. They connect to other cloud platforms without VPN tunnels or on-premise middleware. Azure Logic Apps, AWS Lambda, and similar serverless tools can consume Encompass webhooks directly.
The practical value of Encompass APIs shows up in specific system connections.
Connecting Encompass to Salesforce or Microsoft Dynamics syncs loan status updates to your sales pipeline. Loan officers see borrower progress without switching systems. Lead assignment, milestone notifications, and follow-up triggers all flow through the API.
eRESI's 2025 integration with Encompass Investor Connect lets lenders deliver up to 1,500 Non-Agency and Non-QM loans at once directly from Encompass. Covered Insurance's API platform handles real-time quoting across 50 states and 55+ carriers with embedded compliance monitoring.
OnBase and similar content management systems pull documents from Encompass through the API. Loan files, disclosures, and verification documents sync without manual uploads. Audit trails stay intact across both systems.
Mortgage origination costs average over $11,000 per loan. Every manual step in that process adds cost, time, and error risk. API integrations attack all three.
ICE Mortgage Technology made several moves that affect every Encompass user's integration strategy.
The old SDK integrations hit end-of-life in October 2025. If your custom tools still use SDK calls, they are running on unsupported code. Migration to Developer Connect or Partner Connect APIs is not optional.
The November 2025 service pack addressed webhook delivery consistency. If your team previously built polling-based integrations because webhooks were unreliable, it's worth re-evaluating that architecture.
Automated appraisal ordering through Clear Capital's Automated Collateral Analyzer (Aura) now works directly in Encompass. Configurable workflows trigger appraisal reviews without leaving the platform.
Quandis QBO AI launched in 2025 with agentic AI for compliance-sensitive mortgage servicing. LoanNEX unified primary and secondary lock workflows with real-time alerts inside Encompass. Both signal a shift toward AI handling routine compliance decisions through API-connected tools.
API-first architecture is becoming the default for mortgage technology. Lenders who treat integrations as one-time projects fall behind those who build continuous integration pipelines. Your IT partner should be reviewing Encompass changelog releases quarterly and testing new endpoints as they ship.
Encompass Developer Connect is the API platform for building custom integrations within your own organization. It provides REST endpoints for loan data, pipeline management, contacts, and documents. Partner Connect serves third-party vendors building marketplace products. Both use OAuth 2.0 authentication and RESTful architecture, but Partner Connect adds marketplace distribution and standardized API contracts for vendor products.
The Encompass API uses OAuth 2.0 authentication. Each integration needs an access token tied to a specific Encompass Client ID. API keys are generated in the Encompass admin console and linked to designated API users with explicit role-based permissions. Tokens expire and must be refreshed programmatically to maintain continuous access across automated workflows.
ICE Mortgage Technology deprecated legacy SDK integrations in October 2025. Any custom tools still using SDK calls run on unsupported code and will not receive patches or compatibility updates. Migration to the Developer Connect or Partner Connect REST APIs is required. ICE provides migration documentation and API equivalents for most SDK functions through the developer portal.
Encompass APIs transfer data through encrypted HTTPS connections. All API calls require authenticated tokens with role-based permissions controlling data access. For GLBA compliance, the API enforces the same access controls as the Encompass UI. State-level requirements are handled through the compliance engine within Encompass itself. API integrations inherit those rules when reading or writing loan data.
Yes. Encompass REST APIs and webhooks connect to Microsoft 365 through Azure Logic Apps, Power Automate, or custom Azure Functions. Loan milestone events can trigger Teams notifications. Pipeline data can feed Power BI dashboards for real-time reporting. The integration runs through standard REST and webhook protocols without requiring additional middleware or on-premise servers.
API integrations are not a one-time project. They are infrastructure that compounds value as your loan volume grows. Every manual process you automate today saves time on every loan tomorrow.
Mortgage Workspace helps lenders and mortgage companies design, build, and maintain Encompass integrations that connect to CRMs, compliance tools, and Microsoft 365 environments. We support 750+ financial institutions with managed IT services built for regulated lending.
Talk to a mortgage IT specialist about your integration roadmap.
The loan origination software market hit $6.58 billion in 2025 and is projected to reach $7.35 billion in 2026. That growth is driven by one thing:...
A 2024 MarketWise Advisors study found that lenders using integrated Encompass and CRM platforms saw a $1,056 increase in gross profit per loan. That...