Bing Web Search API error codes: what 401, 403, 410, and 429 actually mean
When a Bing Web Search call fails, read the status code before touching your code.
Bing Web Search API error codes: what 401, 403, 410, and 429 actually mean
TL;DR
When a Bing Web Search call fails, read the status code before touching your code. 401: check the Ocp-Apim-Subscription-Key header value and make sure you are not sending two auth methods at once. 403: check quota usage and whether the key is still active.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
410: switch the request URL to https. 429: slow the request rate, you are over the per-second quota. 400: re-check required parameters, something is missing or malformed.
Context: Official docs (Microsoft Learn, Bing Web Search error codes): the real errors people hit and what they mean. 400 means a parameter is missing or invalid. 401 means the Ocp-Apim-Subscription-Key is missing or wrong, or you sent redundant auth methods at once. 403 means the monthly quota is exceeded, or the authorization is disabled or expired. 410 means you called over plain HTTP instead of HTTPS. 429 means the QPS (queries per second) quota is exceeded.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.