Encompass · Rate Limits

Encompass Rate Limits

ICE Mortgage Technology enforces throttling on the Encompass Developer Connect APIs, but the specific numeric limits are not published on the public reference and are governed per Encompass instance / integration. In practice callers should expect per-instance request-rate throttling (HTTP 429 with Retry-After), plus resource-lock contention on loan writes (Encompass serializes concurrent modifications of the same loan via a resource-lock mechanism). Bulk reads should use the Loan Pipeline cursor endpoints with pagination rather than tight polling, and event-driven integrations should prefer webhooks over polling the pipeline. Deprecated v1 endpoints may carry tighter or sunsetting limits than their v3 replacements.

Encompass Rate Limits is the machine-readable rate-limit profile for Encompass on the APIs.io network, in the API Commons Rate Limits shape.

It captures 4 rate-limit definitions, measuring requests, concurrent writers, rows per request, and access token TTL.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Mortgage, Loan Origination, LOS, ICE Mortgage Technology, and Rate Limiting.

4 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-04.
Written by API Evangelist on 2026-07-04 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
MortgageLoan OriginationLOSICE Mortgage TechnologyRate LimitingQuotas

Limits

API Request Rate instance
requests
not published
Per-instance throttling returns HTTP 429; honor Retry-After and back off.
Loan Write Concurrency loan
concurrent writers
resource-lock enforced
Encompass serializes concurrent modifications to the same loan via resource locks.
Pipeline Result Paging instance
rows per request
cursor/limit governed
Use loanPipeline cursor + start/limit to page large result sets instead of large single pulls.
Token Lifetime application
access token TTL
expires_in (short-lived)
OAuth 2.0 access tokens are short-lived; refresh/re-request before expiry.

Policies

Backoff Strategy
On 429, honor Retry-After and apply exponential backoff with jitter.
Prefer Webhooks Over Polling
Subscribe to resource events (loan.created / updated / deleted / locked / unlocked) instead of polling the pipeline for changes.
Respect Resource Locks
Acquire and release loan resource locks around write operations to avoid contention and lost updates.
Migrate Off v1
Prefer v3 endpoints; deprecated v1 endpoints may be sunset and can carry tighter limits.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/encompass-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.