@@ -63,6 +63,23 @@ If you hit a rate limit, it's expected that you back off from making requests an
6363
6464You can always [ check your rate limit status] ( /v3/rate_limit/ ) at any time. Checking your rate limit incurs no cost against your rate limit.
6565
66+ ## Dealing with abuse rate limits
67+
68+ [ Abuse rate limits] ( /v3/#abuse-rate-limits ) are another way we ensure the API's availability.
69+ To avoid hitting this limit, you should ensure your application follows the guidelines below.
70+
71+ * Make authenticated requests, or use your application's client ID and secret. Unauthenticated
72+ requests are subject to more aggressive abuse rate limiting.
73+ * Make requests for a single user or client ID serially. Do not make requests for a single user
74+ or client ID concurrently.
75+ * If you're making a large number of ` POST ` , ` PATCH ` , ` PUT ` , or ` DELETE ` requests for a single user
76+ or client ID, wait at least one second between each request.
77+ * Requests that create content which triggers notifications, such as issues, comments and pull requests,
78+ may be further limited. Please create this content at a reasonable pace to avoid further limiting.
79+ * When you have been limited, wait the number of seconds specified in the ` Retry-After ` response header.
80+
81+ We reserve the right to change these guidelines as needed to ensure availability.
82+
6683## Dealing with API errors
6784
6885Although your code would never introduce a bug, you may find that you've encountered successive errors when trying to access the API.
0 commit comments