...
Rate Limiting
The USTA institutes per-month, per-hour, per-minute, and per-IP rate limits for each API method, and limits API users to a maximum of five concurrent connections from a single IP address. Our default limits are more than sufficient for nearly all use cases. Please be mindful of these limits. rate limits over a 5 minute time horizon. Traffic is limited on both an overall message and per endpoint basis
Rate limited calls may result in HTTP error status 429 TOO MANY REQUESTS responses.
Overall Traffic Basis
| Item | Value | Description |
|---|---|---|
| Time Horizon | 5 Minutes | Period of time after which the limit count will reset. |
| Limit | 200,000 Requests | Maximum requests a distinct caller can make within the time horizon. |
| Response Code | 429 | HTTP code after limit is reached |
Per Call Basis
| Item | Value | Description |
|---|---|---|
| Time Horizon | 5 Minutes | Period of time after which the limit count will reset. |
| Limit | 200 Requests | Maximum requests a distinct caller can make within the time horizon. |
| Response Code | 429 | HTTP code after limit is reached |
Pagination
...
The default records returned per call is (up to) 25, and the maximum number that can be returned is 100. We provide limit and offset parameters to allow navigation through larger data sets. Responses include a count field, which specifies the total number of records available via pagination. For performance reasons, the offset parameter is limited to a maximum value of 50000.
Here's an example of sequential requests to paginate through the most recent 300 listings, 50 at a time: