What Is Bing Search API? – Definition and How It Works

Learn what the Bing Search APIs were, that Microsoft retired them in 2025, and what the options are now.

The Bing Search APIs were Microsoft's programmatic interface to Bing's index, offering web, image, video, news, and related endpoints. Microsoft retired them in 2025, so anything written about using them before that date describes a service that no longer accepts requests.

1. What They Provided

They were widely used because they were an official, documented, licensed route to a major web index — a category with very few members.

2. Why the Retirement Matters

The Bing Search APIs were the main alternative for anyone who wanted licensed, contractual access to a large web index. Their withdrawal removed that option, and the practical consequences are worth stating plainly:

• Applications built on them had to migrate or stop working.
• The remaining set of official search APIs is smaller than it was.
• Microsoft directed customers toward grounding search results through its Azure AI agent offerings rather than toward a direct replacement search endpoint.

If you are reading a tutorial about api.bing.microsoft.com, check its date. A great deal of surviving documentation describes the retired service.

3. Where Search Data Comes From Now

Grounding through an AI platform. Microsoft's direction of travel is search results delivered as grounding for an AI agent rather than as a general-purpose results API. That suits question-answering, and less well the use cases that want raw ranked results.

Other engines' official APIs. A small number of engines offer programmatic access, generally with quotas and terms narrower than the Bing APIs had.

SERP APIs. Commercial services that return structured search results, which is the category most former Bing API users moved to.

Site-scoped search. Where the requirement is searching a known set of sites rather than the whole web, an index you build yourself is often better than any general engine.

Publisher and vertical APIs. For news, product, or academic data specifically, a domain API frequently beats a general search endpoint.

4. Choosing a Replacement

The questions that determine the answer:

1. Do you need ranked web results, or answers? Grounded AI search gives answers; a SERP API gives results.
2. Which engine's results do you actually need? They differ substantially, and "a search API" is not interchangeable.
3. What volume, and at what cost per query?
4. Which fields matter — organic results only, or features such as local packs, news, and related searches?
5. What are the licence terms for storing and redisplaying results?
6. Is the coverage geographic and language-appropriate for your queries?

Point 5 is the one most often skipped. Search results carry terms about retention and redisplay, and those terms differ by provider.

5. Migration Notes

For anyone moving off the retired APIs, the differences that cause the most rework:

• Response shape. No two providers agree on field names or nesting, so an adapter layer is worth writing rather than threading a new shape through your code.
• Pagination. Offset semantics and page sizes vary.
• Market and language parameters are named and scoped differently everywhere.
• Rate limits and quota accounting differ, so concurrency assumptions do not transfer.
• Result composition. Features present in one provider's output may be absent in another's, which changes what your pipeline can extract.

An adapter with one internal result model, and per-provider mappers into it, is the arrangement that survives the next change.

6. What Has Not Changed

The underlying requirement — programmatic access to search results — is unchanged, and so are the reasons it is hard: search results are location- and time-sensitive, non-deterministic in composition, and licensed rather than free.

Whatever provider you use, the same discipline applies: pin and record location and language, timestamp every observation, store the full result set rather than only your own position, and record the provider and query parameters alongside the data.

7. Summary

The Bing Search APIs provided official programmatic access to Bing's index across web, image, video, news, and entity endpoints, and Microsoft retired them in 2025 — so existing tutorials describe a service that no longer responds.

Replacements fall into grounded AI search, other engines' official APIs, commercial SERP APIs, and self-built site-scoped indexes; choose by whether you need ranked results or answers, check the retention and redisplay terms, and write a provider adapter around one internal result model so the next change is cheaper.

Potential Related Glossary

• Web Crawling
• Parsing
• Data Structure
• Data Fusion