dotloop · Rate Limits

Dotloop Rate Limits

The dotloop Public API v2 enforces a documented per-user rate limit of 100 requests per minute for each client application acting on behalf of a user. Exceeding the limit returns HTTP 429. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers so clients can track and back off against the window.

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

It captures 1 rate-limit definition, measuring requests.

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

Tagged areas include Real Estate, Transaction Management, Zillow Group, Rate Limiting, and Quotas.

1 Limits Throttle: 429
Real EstateTransaction ManagementZillow GroupRate LimitingQuotasThrottling

Limits

Requests Per Minute user
requests · minute
100
Per client application, per user. Exceeding returns HTTP 429.

Policies

Per-User Throttling
Limits are applied per user that a client application acts on behalf of, not globally per app.
Backoff Strategy
Clients should watch X-RateLimit-Remaining / X-RateLimit-Reset and implement exponential backoff on 429 responses.
Event Retention
Webhook events are stored for 90 days and cannot be retrieved after that window.

Sources