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
If an API client continuously fails to abide by rate limits, block them from accessing the service.
Proposal
Block users from generating new clients if any of their clients is on 'cooldown'
Gradually increase the period by which a client cannot access the service should a 429 error be delivered (perhaps there's an in-memory dictionary containing ids of clients which are being ratelimited, and after 5 or so of these errors we start blocking access?)
i.e. 5 minutes of wait time, 10 minutes, 30 minutes, 60 minutes, etc. until their access is permanently revoked.
Questions
Is there already a defined standard for the process of blocking access to the service if abuse is detected?
The text was updated successfully, but these errors were encountered:
If an API client continuously fails to abide by rate limits, block them from accessing the service.
Proposal
Questions
The text was updated successfully, but these errors were encountered: