In This Article
ICE Mortgage Technology kept the Encompass platform moving through 2025 and into 2026. Developer Connect shipped new REST endpoints and webhook notification improvements, Partner Connect expanded its marketplace API coverage, and the company reset the most consequential deadline of all: the legacy SDK transition. If your team is still running legacy Encompass SDK integrations, the clock did not stop, it moved. The grace period began November 1, 2025, SDK retirement was extended to December 31, 2026, and transitional usage fees begin January 1, 2027.
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, and every hour your processors spend re-keying data is an hour they are not closing loans.
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. If you are mapping out how a connected lending stack fits together, our lending tech ecosystem playbook shows where Encompass sits in the larger picture.
How Encompass API Integrations Work
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:
- Developer Connect (EDC): The primary API platform for custom integrations. Provides endpoints for loan data, pipeline management, contacts, and document handling.
- Partner Connect (PCP): Designed for third-party vendors building products that plug into Encompass. Uses the same REST architecture with additional marketplace controls.
- Webhook notifications: Push-based alerts that fire when loan data changes. The November 2025 service pack improved reliability for these notifications.
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.
Why This Matters for Financial Institutions
Banks, credit unions, and mortgage companies operate under examiner scrutiny that most software vendors never face. An Encompass integration is not just a productivity gain, it is a data-handling decision. The OAuth tokens, the role-based permissions, and the encrypted transport are the same controls your IT auditor will want to see documented. Build the integration the way you would build any system that touches borrower data: with access controls, logging, and a clear owner.
Encompass API Integration Types
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.
Third-Party Integrations via Partner Connect
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.
Custom Integrations via Developer Connect
Your internal team or managed IT partner 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. It is also the path most lenders take when they want real-time Power BI dashboards fed directly from live pipeline data.
Cloud-Native Integrations
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. For lenders weighing where these workloads should run, our guide to a hybrid cloud strategy for financial institutions walks through the Azure and on-premise tradeoffs.
Developer Connect (EDC)
Built for integrations your own organization owns and operates. Full access to loan-level data, pipeline queries, contacts, and document APIs. The right choice for internal dashboards, custom compliance checks, and connections to your CRM or Microsoft 365 environment.
Partner Connect (PCP)
Built for third-party vendors distributing products through the Encompass marketplace. Same REST architecture, plus standardized API contracts and marketplace controls. The right choice when you are adopting a vendor product like an appraisal or verification tool rather than building your own.
Connecting Encompass to CRMs, Compliance Tools, and Document Systems
The practical value of Encompass APIs shows up in specific system connections.
CRM Integration
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. The same pattern feeds borrower-facing point-of-sale tools, which is how lenders cut pre-qualification from weeks to minutes.
Compliance and Verification
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-plus carriers with embedded compliance monitoring. Connecting verification and compliance vendors through the API keeps the data your examiners review consistent across systems, the same discipline behind CFPB-proof loan application interfaces.
Document Management
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.
Business Impact of API-Driven Mortgage Workflows
Mortgage origination costs run well over twelve thousand dollars per loan. Every manual step in that process adds cost, time, and error risk. API integrations attack all three.
- Eliminate duplicate data entry: Loan data entered in Encompass flows to your CRM, compliance system, and reporting tools without re-keying.
- Cut processing delays: Automated webhook triggers start the next workflow step the moment a milestone hits. No waiting for someone to check a dashboard.
- Reduce compliance exposure: Automated data transfers maintain consistent records across systems. When regulators audit your loan files, the data matches everywhere.
- Scale without adding headcount: API-driven workflows handle volume increases without proportional staff growth. As loan origination software shifts to an API-first model, lenders who automate now absorb the next volume cycle without hiring for it.
Those gains compound across the whole stack, not just the LOS. For the wider view of how connected lending systems lower cost per loan, see our breakdown of the modern loan origination systems redefining mortgage efficiency and the broader fintech lending ecosystem from borrower apps to the secondary market.
What Changed in 2025 and 2026
ICE Mortgage Technology made several moves that affect every Encompass user's integration strategy.
Legacy SDK Transition (Now December 31, 2026)
The original October 31, 2025 SDK transition deadline did not hold. ICE added a grace period that began November 1, 2025 and extended legacy SDK retirement to December 31, 2026, with transitional usage fees beginning January 1, 2027. The reprieve is real, but the destination has not changed: if your custom tools still use legacy SDK calls, they are running on code with a fixed expiration date. Migration to Developer Connect or Partner Connect REST APIs is not optional, it is now a 2026 project with a hard finish line.
Webhook Reliability Improvements
The November 2025 service pack addressed webhook delivery consistency. If your team previously built polling-based integrations because webhooks were unreliable, it is worth re-evaluating that architecture.
Clear Capital ASO in Encompass (February 2026)
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.
AI-Powered Compliance Workflows
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. For lenders pairing that automation with a mortgage-specialized assistant, ABT's MortgageGuide Copilot agent shows how a tuned model differs from generic Microsoft 365 Copilot for loan work.
What to Plan For
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. Treat 2026 as your legacy SDK exit year, put the December 31, 2026 retirement on the roadmap now, and have your IT partner review Encompass changelog releases quarterly and test new endpoints as they ship.
Is your Encompass integration ready for the 2026 SDK cutover?
With legacy SDK retirement set for December 31, 2026, the lenders who win are the ones who treat integrations as living infrastructure, not one-time projects. ABT designs, builds, and maintains Encompass integrations that connect to CRMs, compliance tools, and Microsoft 365 environments for more than 750 financial institutions.
Frequently Asked Questions
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 extended the legacy Encompass SDK transition. A grace period began November 1, 2025, legacy SDK retirement is set for December 31, 2026, and transitional usage fees begin January 1, 2027. Any custom tools still using legacy SDK calls run on code with a fixed end date and must migrate to the Developer Connect or Partner Connect REST APIs. 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.