...
The simplest way to access the API is via use of cURL. Any language or client that supports HTTPS can be used to call the API.
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 limited calls may result in HTTP error status 403 responses.
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:
| Panel |
|---|
https://services.usta.com/v1/customer/me/roles?limit=50&offset=0 https://services.usta.com/v1/customer/me/roles?limit=50&offset=50 https://services.usta.com/v1/customer/me/roles?limit=50&offset=100 https://services.usta.com/v1/customer/me/roles?limit=50&offset=150 https://services.usta.com/v1/customer/me/roles?limit=50&offset=200 https://services.usta.com/v1/customer/me/roles?limit=50&offset=250 |
Lookup Behavior
Standard behavior when looking up elements in the API result in HTTP error status 404 NOT FOUND when an element does not exist. In some cases, an API can result in HTTP status 200 where the result will contain an empty result set. Where the behavior deviates, the API reference will denote the behavior,
...