Document secondary rate limits, update rate limit docs (#45135)
Co-authored-by: Ivan Žužak <izuzak@gmail.com> Co-authored-by: Jess Hosman <1183847+jhosman@users.noreply.github.com>
This commit is contained in:
@@ -15,7 +15,7 @@ autogenerated: rest
|
||||
|
||||
## About rate limits
|
||||
|
||||
You can check your current rate limit status at any time. For more information about rate limit rules, see "[AUTOTITLE](/rest/overview/resources-in-the-rest-api#rate-limiting)."
|
||||
You can check your current rate limit status at any time. For more information about rate limit rules, see "[AUTOTITLE](/rest/overview/rate-limits-for-the-rest-api)."
|
||||
|
||||
The REST API for searching items has a custom rate limit that is separate from the rate limit governing the other REST API endpoints. For more information, see "[AUTOTITLE](/rest/search)." The GraphQL API also has a custom rate limit that is separate from and calculated differently than rate limits in the REST API. For more information, see "[AUTOTITLE](/graphql/overview/resource-limitations#rate-limit)." For these reasons, the API response categorizes your rate limit. Under `resources`, you'll see objects relating to different categories:
|
||||
|
||||
@@ -35,6 +35,6 @@ The REST API for searching items has a custom rate limit that is separate from t
|
||||
|
||||
- The `actions_runner_registration` object provides your rate limit status for registering self-hosted runners in {% data variables.product.prodname_actions %}. For more information, see "[AUTOTITLE](/rest/actions/self-hosted-runners)."
|
||||
|
||||
For more information on the headers and values in the rate limit response, see "[AUTOTITLE](/rest/overview/resources-in-the-rest-api#rate-limit-http-headers)."
|
||||
For more information on the headers and values in the rate limit response, see "[AUTOTITLE](/rest/overview/rate-limits-for-the-rest-api)."
|
||||
|
||||
<!-- Content after this section is automatically generated -->
|
||||
|
||||
Reference in New Issue
Block a user