You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a call to /api/request/id or api/request/bestmatch is made, the body should return a TimeRemaining field representing the rounded integer seconds until they can make another request.
For example, if the server administrator sets a timeout of 180, and the user tries to make a request five seconds after they just made their first request, the response field of the code 429 should include TimeRemaining: 175.
This would enable us to do things like have the UI disable and re-enable the request buttons automatically, and allow other clients like CadenceBot to report to users how much longer they have to wait until they can make another request. We had this feature in v4, so this issue will mostly be a re-implementation on the new Redis rate limit database.
The text was updated successfully, but these errors were encountered:
When a call to
/api/request/id
orapi/request/bestmatch
is made, the body should return aTimeRemaining
field representing the rounded integer seconds until they can make another request.For example, if the server administrator sets a timeout of
180
, and the user tries to make a request five seconds after they just made their first request, the response field of the code 429 should includeTimeRemaining: 175
.This would enable us to do things like have the UI disable and re-enable the request buttons automatically, and allow other clients like CadenceBot to report to users how much longer they have to wait until they can make another request. We had this feature in v4, so this issue will mostly be a re-implementation on the new Redis rate limit database.
The text was updated successfully, but these errors were encountered: