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, conforming to the API Commons Rate Limits specification.

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

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 Throttle: 429
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