Bridge Interactive · Rate Limits

Bridge Interactive Rate Limits

The Bridge API paginates responses and constrains result-set size rather than publishing a single fixed per-second request quota. The Bridge Web API returns paged bundles controlled by limit/offset, and the RESO Web API (OData) pages with $top/$skip; result sets beyond 10,000 records must use the Property replication endpoint for full extraction. Specific per-account request-rate ceilings are governed per dataset and are not reconciled in this artifact.

Bridge Interactive Rate Limits is the machine-readable rate-limit profile for Bridge Interactive on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring records and requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Real Estate, MLS, RESO, Listings, and Property Data.

4 Limits Throttle: 429
Real EstateMLSRESOListingsProperty DataRate LimitingQuotasThrottling

Limits

Bridge Web API Page Size request
records
see provider documentation
Controlled by the limit parameter with offset-based pagination.
RESO Web API Page Size request
records
see provider documentation
Controlled by $top / $skip; v3 changes $top to represent total collection size.
Replication Threshold dataset
records
10000
Result sets larger than 10,000 records must use the Property replication endpoint.
Per-Account Request Rate account
requests
see provider documentation
Governed per dataset and access token; specific ceilings not reconciled here.

Policies

Pagination
Page through large result sets with limit/offset (Bridge Web API) or $top/$skip (RESO Web API).
Replication
Use the Property replication endpoint to synchronize datasets exceeding the 10,000-record threshold.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor any 429 throttling responses.

Sources