Missing anchor `rate-limiting` for getting-started-with-the-rest-api

[jsoref]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/rest/using-the-rest-api/getting-started-with-the-rest-api#rate-limiting

What part(s) of the article would you like to see updated?

It seems that GitHub's backend has hallucinated a #rate-limiting anchor. Since it expects one, the docs clearly need to have one.

Additional information

My regression tests tripped on this url: https://github.com/check-spelling-sandbox/check-spelling/actions/runs/23625208627/job/68812871237:

#   Failed test 'apply.pl (stdout) imaginary-repository'
#   at t/Apply.t line 319.
#                   'Apply.t: Unknown error, please check the list of known issues https://github.com/check-spelling/check-spelling/issues?q=is%3Aissue%20apply.pl and file a bug to https://github.com/check-spelling/check-spelling/issues/new?title=%60apply.pl%60%20scenario&body=Please%20provide%20details+preferably%20including%20a%20link%20to%20a%20workflow%20run,%20the%20configuration%20of%20the%20repository,%20and%20anything%20else%20you%20may%20know%20about%20the%20problem%2e
# {
# 	"message": "API rate limit exceeded for installation. If you reach out to GitHub Support for help, please include the request ID 5006:2A7FF8:1BED75F:70CA5F5:69C5DD47 and timestamp 2026-03-27 01:28:39 UTC. For more on scraping GitHub and how it may affect your rights, please review our Terms of Service (https:\/\/docs.github.com\/en\/site-policy\/github-terms\/github-terms-of-service)",
# 	"documentation_url": "https://docs.github.com/en/rest/using-the-rest-api/getting-started-with-the-rest-api#rate-limiting",
# 	"status": "403"
# }

I intend to fix my code to better handle this error, but the docs should have the anchor (w/o them, how would I or someone else know what to do?).

[Sharra-writes]

@jsoref Looks like someone already opened a PR for this. I'd be interested to know if you feel it solves the problem, but I'm also going to go ask the people who deal with APIs if they think it does.

[jsoref]

Looks good enough to me

[jsoref]

Fwiw, github support says:

Thanks for getting in touch. It looks as though you've opened an issue in the correct repository already!

So, it sounds like they're fine with this change.