Introduction

The mortgage industry in the United States has always been complex. Between borrower expectations, compliance mandates, and the need for speed in loan origination, lenders rely heavily on technology platforms to stay competitive. At the heart of this ecosystem sits Encompass® by ICE Mortgage Technology a loan origination system (LOS) trusted by thousands of lenders nationwide.

But Encompass is not just an LOS; its real value lies in how it connects with external services. From ordering credit reports to requesting mortgage insurance and handling appraisals, Encompass integrations enable everything to happen within a single workflow.

Historically, these integrations were powered by the Encompass SDK, PSDK, and ePass connectors. However, ICE has announced a major shift: support for SDK, PSDK, ePass, and legacy TQL will officially end on October 31, 2025.

This is more than a routine update. It’s a deadline that forces every U.S. lender and vendor to rethink how their systems connect to Encompass. The future lies in Partner Connect APIs cloud-based, RESTful services that are modern, secure, and designed for long-term scalability.

In this blog, we’ll cover:

What Encompass integration services are and why they matter
The risks of ignoring the 2025 SDK sunset
The benefits of Partner Connect APIs
Real-world adoption examples
A step-by-step migration strategy for lenders and vendors
SEO insights for staying visible in the U.S. mortgage tech landscape

Understanding Encompass Integration Services

Encompass integration services are essentially digital pipelines that connect the LOS with third-party providers. Instead of manually uploading documents or re-entering borrower data, integrations ensure data flows automatically and securely.

For example:

A loan officer orders a credit report directly inside Encompass.
An underwriter requests mortgage insurance with one click.
Closing agents receive title data without leaving the LOS.

These workflows not only save time but also reduce human error, keep loan files centralized, and improve compliance tracking.

The Two Integration Models

Legacy SDK / ePass
- Relied on proprietary software kits and desktop connections
- Depended on Encompass release cycles for updates
- Worked primarily in local environments
- Rigid and increasingly outdated in the cloud era
Partner Connect APIs (EPC)
- Cloud-native REST APIs
- Support Encompass Web, Desktop, Consumer Connect, and TPO Connect
- JSON payloads and OAuth 2.0 security
- Vendor-controlled release cycles for faster innovation
- Scalable, resilient, and automation-friendly

The difference is like comparing dial-up internet to modern fiber optics both connect you, but one is built for today’s speed and reliability.

Why the 2025 SDK Sunset Is a Big Deal

ICE Mortgage Technology has been clear: after October 31, 2025, SDK and ePass integrations will no longer be supported.

This carries significant risks:

Operational disruption: If your LOS depends on SDK connectors, workflows could break overnight.
Compliance gaps: Unsupported tools may not meet evolving regulatory standards.
Increased costs: Staff may need to revert to manual processes, slowing loans and raising expenses.
Competitive disadvantage: Early adopters of Partner Connect will move faster, close more loans, and deliver better borrower experiences.

Simply put: the countdown is on, and lenders who don’t prepare now risk serious setbacks in 2025.

Benefits of Partner Connect APIs

Migrating to EPC is not just about compliance it’s about unlocking the future of mortgage tech.

1. Unified Cross-Platform Support

A single integration works across Encompass Desktop, Web, Consumer Connect, and TPO Connect. No more fragmented builds.

2. Vendor Agility

Vendors can release improvements independently, without waiting for ICE’s product cycle. This accelerates innovation.

3. Automation at Scale

Lenders can automate repetitive tasks like ordering appraisals, pulling credit, or validating borrower data. This reduces manual errors and cuts processing time.

4. Cloud-Native Resilience

APIs are built for scalability. Whether you’re handling 100 loans a month or 10,000, EPC adjusts seamlessly.

5. Compliance and Security

OAuth 2.0 and encrypted payloads ensure secure data exchange, critical in an industry governed by strict regulations.

6. Future-Proof Innovation

EPC lays the foundation for advanced tools like AI-powered underwriting, eClosings, and blockchain-backed verifications.

Real-World Adoption Examples

Many vendors and lenders are already using EPC to reimagine workflows:

Mortgage Insurance Center: ICE introduced MI Center inside Encompass, powered by EPC, allowing lenders to compare MI products and place orders instantly.
First American Title: Automates title and settlement orders directly from Encompass, reducing turnaround times and errors.
Core10: A tech consultancy helping lenders migrate from SDK to EPC, providing planning, development, QA, and ongoing support.

These use cases show EPC is not just theoretical it’s live, delivering tangible business results today.

Migration Strategy for Lenders and Vendors

Migrating to EPC can look overwhelming, but a structured roadmap makes it manageable.

Step 1: Audit Current Integrations

Document every SDK/ePass connection. Rank them by business impact.

Step 2: Prioritize Critical Services

Migrate compliance-sensitive integrations first (credit, MI, title).

Step 3: Define Your Build Approach

Decide whether to handle development in-house or outsource to an EPC-certified partner.

Step 4: Sandbox Testing

Leverage the Encompass Developer Connect Sandbox to test APIs, validate payloads, and simulate workflows before production.

Step 5: Deployment & Monitoring

Use logging and monitoring tools (Splunk, ELK, Datadog) to track performance, latency, and error rates.

Step 6: Training & Documentation

Ensure staff understand new workflows and IT teams have updated documentation.

Choosing the Right Integration Partner

For many lenders, working with an experienced EPC integration partner makes the transition smoother.

Look for:

Proven EPC integration portfolio
Knowledge of U.S. mortgage compliance
Ability to provide end-to-end delivery (strategy → code → testing → support)
Integration with DevOps workflows (CI/CD pipelines, automated QA)

Conclusion

The sunset of SDK/ePass in 2025 marks a turning point for U.S. mortgage lenders. While the deadline may feel distant, the reality is clear: every lender relying on legacy integrations must act now to ensure business continuity.

The good news? Migrating to Partner Connect APIs is not just a compliance checkbox it’s an opportunity to build a faster, smarter, and more scalable mortgage business.

By embracing EPC, lenders can:

Automate workflows
Strengthen compliance
Deliver better borrower experiences
Position themselves for future innovations

The countdown is on. The lenders who act today will lead tomorrow.

Encompass® Integration Services: Why U.S. Lenders Must Transition to Partner Connect APIs Before 2025