Trestle Rate Limits
Trestle publishes concrete baseline quotas and returns live quota headers on every response — including on anonymous 401s. Quotas are calculated per product / feed-type pair, not per account: one technology provider with an IDX - WebAPI connection to one MLS and an IDX Plus - WebAPI connection to another gets a separate quota for each connection, and a connection's quota grows as more MLSs are added to it. Media (public MediaURL) requests are metered against a separate, larger quota than API queries.
Trestle Rate Limits is the machine-readable rate-limit profile for Trestle on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions, measuring requests_per_hour and requests_per_minute.
Limit state is signalled in the minuteQuotaLimit, hourQuotaLimit, hourQuotaResetTime, and quotaType response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled.
Tagged areas include Rate Limiting, Real Estate, and MLS.
minuteQuotaLimithourQuotaLimithourQuotaResetTimequotaType
Limits
Sources
- https://trestle-documentation.corelogic.com/webapi.html
- https://trestle-documentation.corelogic.com/webapi-at-scale.html
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.