Corelogic Rate Limits
Trestle does not publish hard per-second rate limits in its public documentation; instead it imposes per-request result-size caps and a documented "Growing to Scale" pattern (Replication mode) for high-volume consumers. The documented caps are: $top defaults to 10 and maxes at 1000 records per response (300000 records for key-only queries), $apply=groupby returns at most 10000 unique values, and Replication=true enables bulk replication for datasets exceeding 1 million rows. Quota enforcement is signaled with HTTP 429.
Corelogic Rate Limits is the machine-readable rate-limit profile for CoreLogic (Cotality) on the APIs.io network, in the API Commons Rate Limits shape.
It captures 8 rate-limit definitions, measuring records_per_response, rows, and seconds.
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 response codes documented for badRequest, unauthorized, notFound, throttled, quotaExceeded, serverError, and gatewayTimeout.
Tagged areas include CoreLogic, MLS, OData, Quotas, and Rate Limiting.
generated, dated 2026-05-23.
Limits
Sources
- https://trestle-documentation.corelogic.com/webapi-reference.html
- https://trestle-documentation.corelogic.com/webapi-at-scale.html
- https://trestle-documentation.corelogic.com/webapi.html
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.