Review the Cotality migration notice that announced the Trestle API URL change from the legacy CoreLogic domain to the new Cotality-hosted base URL prior to the end-of-2025 migration deadline
Update all hardcoded Trestle API base URLs in your integration code, configuration files, and environment variables to the new Cotality endpoint, preserving all URL path segments after the base domain
Verify that existing OAuth 2.0 client credentials and access token flows continue to function against the new endpoint; token endpoint URLs are typically also updated during domain migrations
Test authentication, metadata retrieval ($metadata endpoint), and at least one RESO Web API OData query against the new endpoint in a staging environment before switching production traffic
Update any IP allowlist or firewall rules in your network infrastructure to permit outbound traffic to the new Cotality domain IP ranges, since the new domain may resolve to different server infrastructure
Monitor the first 48 hours of production traffic on the new endpoint for any 4xx or 5xx error rate increases, SSL certificate errors, or response time regressions compared to baseline on the old endpoint
Known gotchas
OAuth token endpoint URLs are often overlooked during domain migrations; an integration that updates the data API URL but not the token URL will successfully authenticate against the old token endpoint temporarily but may fail when the old endpoint is eventually decommissioned
Trestle serves multiple MLSs; some MLSs may complete migration on different schedules within the overall Cotality transition—do not assume all data source connections migrate simultaneously and verify per-MLS endpoint status during the transition window
CDN and DNS caching can cause some requests to reach the old endpoint even after updating configuration; clear DNS cache and any application-level HTTP client connection pools, and add TTL-aware validation to confirm the active endpoint host is the new Cotality domain
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp