Brandon Harvie
October 21, 2022 | Fixes | Brandon Harvie

Fix: API Rate Limiting Reimplemented

Update - Friday, January 27th, 2023:

We will deploy rate limiting to our staging environment, and you can begin testing starting next week.

The staging endpoint is, and the environment will be available for testing from January 30th to February 3rd.

We will monitor feedback and share more information after the testing. If you have any questions, please feel free to contact for assistance. We appreciate your patience.

Update - Thursday, October 27th, 2022:

We originally planned to re-implement the rate limits on Wednesday, October 26th. Some wineries noticed issues when we tried to re-implement the rate limits. We have rolled back the update and are currently investigating the matter. Our team is working diligently towards a fix.

If you have questions about the re-implementation or are having any issues with rate limits, please feel free to contact for assistance. We appreciate your patience.

If you have previously tried to return a large set of data via our webservices, you may have noticed an error with the request. This was caused by our infrastructure being overwhelmed by repeated requests and our rate limits not functioning correctly. We have re-implemented our rate limits to help prevent these errors and improve overall platform performance. These rate limits are:


  • Number of maximum concurrent requests per username per second: 6 requests
  • Number of maximum requests per username at the last minute: 300 requests


As this change can be crucial for some wineries, we wanted to ensure we let wineries know ahead of the change. We plan to make this change on October 26th @ 5:00 am PST.

For more information about rate limits, check out the documentation.

If you have any questions, please get in touch with, and we will be happy to assist.


Commenting has been turned off.