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
Copy file name to clipboardExpand all lines: README.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,8 @@ To get an API token, log in with any oauth provider and enter the dashboard. Cop
34
34
The way ratelimits work differs based on whether redis is being used or not.
35
35
If redis is in use, the window method is used, where you have X requests available in a certain timeframe.
36
36
If redis is NOT in use, the leaky bucket method is used, where you gain requests after every X seconds.
37
-
The ratelimit headers will differ a slight bit depending on the method in use (ex x-ratelimit-reset is not applicable to the leaky bucket, and will always be 0)
37
+
The ratelimit headers will differ a slight bit depending on the method in use (ex x-ratelimit-reset is not applicable to the leaky bucket, and will always be 0).
38
+
You can always tell what method is being used via the `X-Ratelimit-Strategy` header. If this header returns `ignore`, ratelimits are not applicable to the request (ex if using an admin account).
38
39
39
40
All API responses have ratelimit information associated with them:
40
41
-`x-ratelimit-available`: How many API calls you have left before being ratelimited.
0 commit comments