← Back to all docs

Ellie Mae API

Ellie Mae, now operating as ICE Mortgage Technology (a subsidiary of Intercontinental Exchange after its 2020 acquisition), is a mortgage software-as-a-service company that automates loan origination, processing, underwriting, and regulatory compliance for residential mortgage lenders. This page is an independent design exercise that asks what a well-designed Ellie Mae API could look like: the resources it would expose, the authentication it would need, and the workflows it could unlock. Below: a hypothetical endpoint design, the technical requirements a production implementation would face, the use cases programmatic access could serve, and where to start if your team needs this kind of access today.

By Alex KlarfeldJuly 8, 2026
Ellie Mae API

This page is an independent analysis by Supergood of what a well-designed Ellie Mae API could look like. It draws on publicly available information, vendor materials, and general integration experience in this category. Nothing on this page describes an existing Ellie Mae product, and Supergood is not affiliated with or endorsed by the vendor. If the vendor offers an official API, we highly recommend it.

What is Ellie Mae?

Ellie Mae, now operating as ICE Mortgage Technology (a subsidiary of Intercontinental Exchange after its 2020 acquisition), is a mortgage software-as-a-service company that automates loan origination, processing, underwriting, and regulatory compliance for residential mortgage lenders. Its flagship Encompass platform is an end-to-end digital lending system of record that lenders use to originate, sell, and purchase loans, supported by a portfolio of compliance, pricing, and customer-engagement products.

Core product families include:

  • Encompass (flagship digital lending platform and loan origination system of record)
  • Encompass Consumer Connect and TPO Connect (borrower and third-party originator portals)
  • AllRegs (online database of government and conventional lending guidelines and reference data)
  • Velocify (lead and customer engagement platform)
  • Mavent (automated regulatory compliance review) and Total Quality Loan workflows
  • Data & Document Automation (Capsilon) for document recognition and eFolder workflows

An API for a platform like this would naturally organize around its core data entities:

  • Loans, Applications, Borrowers, Co-borrowers, Loan Fields
  • Pipeline Views, Loan Folders, Milestones, Conditions
  • Documents, eFolder Attachments, Disclosures, eClose packages
  • Product and Pricing results, Rate Locks, Compliance Reviews
  • Contacts, Loan Officers, Service Orders, Investor Loans

The Ellie Mae Integration Challenge

Lenders run mission-critical origination workflows on Encompass every day, but turning them into reliable API-driven automation is non-trivial:

  • Client-only access: Encompass Developer Connect is intended for licensed Encompass clients, so API access is gated behind your instance, entitlements, and admin configuration
  • Loan field model complexity: Encompass exposes thousands of canonical loan fields and custom fields whose IDs and meanings vary by lender configuration
  • OAuth and client credential setup: Obtaining API keys, client IDs, and instance scopes requires coordination with ICE and your Encompass administrator
  • Concurrency and payload limits: Developer Connect enforces concurrency limits and webhook payload-size constraints that have to be respected at scale
  • Milestone and condition logic: Loan progress is driven by milestones, conditions, and business rules that differ across lenders and loan programs
  • Document and eFolder handling: Disclosure packages, eFolder attachments, and eClose documents need careful upload, retrieval, and template handling

What a Ellie Mae API Could Look Like

If Ellie Mae exposed a modern, general-purpose API, the integration challenges above suggest what it would need to get right. This is a design sketch, not documentation of anything that exists today:

  • First-class authentication: session handling with support for MFA and enterprise sign-on where the platform uses them
  • Consistent resources: normalized JSON schemas and pagination across the platform's core objects
  • Reliable writes: idempotency keys and validation that mirrors the platform's own workflow rules
  • Entitlement awareness: endpoints scoped to what each customer's licensing actually permits

The endpoint sketches, technical requirements, and use cases below flesh out this hypothetical design.

How AI agents could connect to software like Ellie Mae: MCP servers for software without a public API →

Need This Kind of Access Today?

If your team needs this kind of access today, Supergood builds integrations on request, one customer at a time. We act at the direction of our customers, within the access they already hold. Customers bring their own accounts, licenses, and entitlements. If the vendor offers an official API, we highly recommend it.

  1. Schedule an Integration Assessment
    A 30-minute session to review your product mix, licensing, and authentication model.
  2. Scope the Integration
    We design the access pattern around your workflows and entitlements.
  3. Deploy with Monitoring
    Go live with continuous monitoring as your platforms evolve.

Ellie Mae on the API Report Card

Potential API Endpoints

Authentication

POST/authenticate

Would authenticate to an Encompass instance via OAuth client credentials or user login and obtain an access token for downstream calls.

Loans

GET/loans

Would retrieve loans with their field values, borrower data, and milestone status, filtered by loan folder, date, or pipeline criteria.

Loans

POST/create_loan

Would create a new loan in Encompass from an application template and seed initial field values and borrower information.

Loans

PATCH/update_loan

Read, write, and update field values on a single loan or multiple loans, including custom and canonical fields.

Pipeline

GET/pipeline

Would query the loan pipeline using specific fields and filters to view loan status, milestones, and assignments across the organization.

Documents

GET/documents

Would list and download eFolder documents, disclosure packages, and attachments associated with a loan.

Use Cases

Sync loan and pipeline data into your warehouse

- Pull active loans, field values, and milestone status from Encompass into a single data warehouse - Stream pipeline changes to downstream BI, reporting, and analytics tools - Reconcile borrower, co-borrower, and contact records across systems

Automate loan creation and field updates

- Create loans from upstream lead and point-of-sale systems without manual entry - Read, write, and update canonical and custom field values across one or many loans - Trigger milestone advances and condition updates as documents are received

Streamline document and disclosure workflows

- Upload and retrieve eFolder attachments and disclosure packages programmatically - Route eClose and Data & Document Automation outputs to the right loan folder - Track document conditions and clear them as supporting files arrive

Keep compliance and pricing data in sync

- Pull product-and-pricing and rate-lock results into downstream pricing tools - Surface Mavent compliance review outcomes alongside loan records - Reconcile AllRegs guideline references against loan program eligibility

Technical Requirements

Authentication

Would require OAuth client credentials and user login, including MFA, with managed session handling

Connectivity

Would build on encompass Developer Connect REST APIs plus authenticated browser flows where capabilities aren't exposed via API

Response format

Normalized JSON across Loan, Pipeline, Field, Document, and Pricing objects

Rate limits

Adaptive throttling tuned to Developer Connect concurrency limits to avoid lender-side restrictions

Session management

Would need automatic token refresh, MFA handling, and credential rotation

Data freshness

Near real-time pulls for loans and pipeline with optional scheduled batch syncs

Security

Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging

Webhooks

Event-style callbacks for loan field changes, milestone updates, and document events

Latency

Design target: sub-second reads on cached entities; multi-second writes when posting field and document updates

Throughput

Design target: horizontally scaled workers sized to high-volume origination pipelines

Reliability

Retry, backoff, and idempotency keys for loan creation and field-update transactions

Versioning

Clear versioning and change management would matter as Ellie Mae evolves

Frequently asked questions

Ellie Mae now operates as ICE Mortgage Technology following its acquisition by Intercontinental Exchange, but the Encompass platform and its developer APIs remain the core of the offering.

Availability of official interfaces varies by product, plan, and licensing. Many platforms in this category gate access behind partner programs or paid modules, and there is often no broadly available, self-serve public API. Check the vendor's developer resources for current offerings.

The hard parts would be authentication (MFA, session management, enterprise controls), consistent schemas across the platform's products, and write semantics that reconcile the way the platform's own workflows do.

No. This page is an independent analysis by Supergood and is not affiliated with, sponsored by, or endorsed by the vendor. All product names and trademarks belong to their respective owners and are used for identification only. Nothing here documents an actual Ellie Mae product or service.

Supergood acts at the direction of its customers, within the access those customers already have. We respect each customer's agreements with their software vendors, and how those agreements apply to a customer's use is a determination the customer makes. If the vendor offers an official API, we highly recommend it.

Supergood builds managed API access to enterprise software for customers on request, scoped to each customer's own licensing and entitlements. If your team needs programmatic access to a platform like this, schedule an integration assessment to discuss options.

Ready to get a real API?