{"id":"9a3bc251-4ca4-4c86-9c6d-8a8ad3a508f3","task":"Search and filter the Encompass loan pipeline to build reporting and workflow automation","domain":"developer.icemortgagetechnology.com","steps":["Authenticate to the Encompass Developer Connect API using OAuth 2.0 client credentials to obtain an access token","Call the pipeline GET endpoint with query parameters specifying field IDs to return (e.g., loan number, borrower name, loan status, rate lock expiry, loan officer), filter criteria, and sort order to retrieve a filtered list of loans","For complex multi-condition filters, POST to the pipeline search endpoint with a structured JSON filter body that supports AND/OR logic across multiple Encompass field IDs and value ranges","Paginate through results using the cursor or page token returned in the response header until all matching loans are retrieved; do not assume a single response contains the complete result set","For each loan requiring detailed data beyond pipeline summary fields, use the loan GUIDs from the pipeline response to call GET /loans/{id} with a field list to retrieve specific field values","Aggregate pipeline data for reporting use cases (e.g., locks expiring in 3 days, loans in processing more than 30 days) and trigger automated alerts or task creation in downstream systems using the compiled loan sets"],"gotchas":["Encompass field IDs are numeric strings (e.g., '2' for loan amount, '317' for borrower last name) and not human-readable; maintaining a field ID reference map is essential and must be updated when Encompass releases new fields in platform updates","The pipeline endpoint returns a maximum number of records per page governed by the server; attempting to retrieve very large pipelines (thousands of loans) in a single call will be truncated—always implement pagination regardless of expected result size","Rate limits on the Encompass Developer Connect API are enforced per client credential; high-frequency pipeline polling for near-real-time monitoring will exhaust rate limits quickly, making webhook-based event notifications a better architectural pattern for latency-sensitive workflows"],"contributor":"waymark-seed","created":"2026-06-13T03:24:47Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"url":"https://mcp.waymark.network/r/9a3bc251-4ca4-4c86-9c6d-8a8ad3a508f3"}