Bing Search API after the v7 retirement
Microsoft retired the Bing Search API on 11 August 2025 and stopped issuing keys for it. Search1API keeps Bing web results reachable over HTTP, in the same request shape as its other engines.
Endpoint
Results arrive in the same JSON shape as every other engine, so existing parsing continues to work.
Clean titles, without the scraping artefacts.
The result description as Bing renders it.
Set crawl_results and the top results return markdown.
Useful for
Migration off v7 / AI answers / Cross-checking
The index behind more than one front end
Set `search_service` to `bing` and the results come from Bing. The endpoint, the authentication, and the response shape are the same as every other engine, and no Azure subscription is involved.
A path off the retired v7 API
Microsoft decommissioned the Bing Search APIs, including v7 and Custom Search, on 11 August 2025. Existing keys stopped working and no new ones are issued.
No Azure resource to provision
Requests are billed against Search1API credits rather than an Azure Cognitive Services resource, so there is no subscription, region, or pricing tier to configure.
A second general ranking
Bing draws on its own index, so it surfaces pages a Google-only pipeline can miss. Running both is a coverage strategy rather than a redundant call.
Standard Search parameters
`max_results` up to 50, plus `include_sites`, `exclude_sites`, and `time_range`.
What is a Bing search API in 2026?
A Bing search API is an HTTP interface that returns Bing web results as structured data. Microsoft used to sell this directly as the Bing Search API v7 through Azure, and retired it on 11 August 2025: instances were decommissioned, existing keys stopped working, and Microsoft pointed customers at its AI grounding products instead — which return a synthesised answer rather than a ranked list of results. Applications that still need the Bing ranking now reach it through a search API. Search1API exposes Bing as one of the search services on its Search endpoint, returning titles, links, and snippets in the same JSON shape it returns for its other engines, with optional page content in the same request.
Typical workflow
Microsoft retired the Bing Search API on 11 August 2025 and stopped issuing keys for it. Search1API keeps Bing web results reachable over HTTP, in the same request shape as its other engines.
Send a query with `search_service` set to `bing`.
Read the structured result list of titles, links, and snippets.
Set `crawl_results` when the answer needs page content rather than links.
One request, Bing results as JSON
A single call searches Bing and returns the same result shape as every other engine, so code written against the retired v7 API can be repointed rather than rewritten around a different response format.
bash
Best for
Applications migrating off the retired Bing Search API v7.
AI assistants that want a ranked result list rather than a synthesised answer.
Cross-checking a Google result set against a second general index.
Research and monitoring tools that need Bing’s ranking specifically.
FAQ
Is the Bing Search API still available?
Not from Microsoft. The Bing Search APIs, including v7 and Custom Search, were retired on 11 August 2025. Instances were decommissioned, existing keys stopped working, and new keys are not issued. Search1API reaches Bing results through its own Search endpoint instead.
What did Microsoft recommend instead?
Microsoft pointed customers toward its AI grounding products, which return a synthesised answer rather than a ranked list of web results. That is a different shape of output, and it does not fit applications that need the result list itself.
Do I need an Azure subscription?
No. Authentication is your Search1API key. The request is a POST to https://api.search1api.com/search with `search_service` set to `bing`.
What does a Bing search cost?
One credit per search, and one additional credit for each page retrieved successfully through `crawl_results`. At the base top-up rate of $1 for 1,000 credits, that is $1 per 1,000 searches. Signup includes 100 free credits with no credit card, and top-up credits do not expire.
How does this differ from the Google engine?
Bing maintains its own index and ranking, so the same query returns a different set of pages and a different order. The Search endpoint accepts an array of query objects, so both can be sent in one batch and compared.
Is Yahoo the same as Bing here?
Largely, yes. Yahoo’s organic web results are supplied by Bing under their long-standing search alliance, so the two overlap heavily. Use `bing` unless you specifically want the Yahoo result set.