Rate Limiting
- 08 Apr 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Rate Limiting
- Updated on 08 Apr 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
WineDirect enforces API rate limits for its APIs. Rate limit configuration includes a per-minute request limit per webservice account on all read endpoints. Limits are currently set to but subject to change (you can always refer to the "x-rate-limit-limit" header to view the up-to-date limits):
- Number of maximum requests per username at the last minute: 480 requests
There also may be endpoints with higher limits than others (again, refer to the headers for those exact limits).
We return rate limit headers in our API responses to allow developers to monitor their API usage.
| Header Name | Description |
|---|---|
x-rate-limit-limit | You can make the maximum number of requests per rate limit window. |
x-rate-limit-remaining | The number of requests remaining in the current rate limit window. |
x-rate-limit-reset | The time at which the current rate limit window resets in UTC epoch seconds. |
If you exceed your rate limit, your request will be rejected. An "HTTP 429 (Too Many Requests)" response will be returned. It would be best if you waited until the end of the current rate limit window before making any more requests, which we'd suggest building logic into your application.
Was this article helpful?
