Background
FY25/26 KR 5.2 focuses on bringing API endpoints onto common infrastructure. The main aspect of that focuses on routing all traffic through a common API Gateway. To that end, the final set of endpoints that must be rerouted through the common gateway are those remaining on the historic API Gateway (aka: those documented through the API Portal). While the majority of these endpoints follow the same rate limits, the Lift Wing API is an outlier with a custom rate limit policy. To complete the rerouting work, we need to be able to support higher limits for these endpoints, potentially with different thresholds based on user class.
Conditions of acceptance
Update rate limits for Lift Wing to the following:
- Unidentified - 50k/hr; 15/s
- Browser - 50k/hr; 50/s
- Authenticated - 100k/hr; 100/s
- WMCS - 200k/hr; 200/s
- Approved bot - 200k/hr; 200/s
- Known client - 200k/hr; 200/s
The higher limits should only apply for the Lift Wing endpoints. Lift Wing routes are designated by /service/lw in the path.
One enabled, pay close attention to WME traffic in particular, as they represent the current highest volume consumer.