Client API migration

Move your Bing v7 client to Search1API

Update the endpoint and subscription key in supported Bing v7 clients. Keep the webPages.value result format with Search1API’s Bing-backed compatibility API.

Open WebUI — bash diff
-BING_SEARCH_V7_ENDPOINT="https://api.bing.microsoft.com/v7.0/search"
-BING_SEARCH_V7_SUBSCRIPTION_KEY="YOUR_BING_KEY"
+BING_SEARCH_V7_ENDPOINT="https://api.search1api.com/compat/bing/v7.0/search"
+BING_SEARCH_V7_SUBSCRIPTION_KEY="YOUR_SEARCH1API_KEY"

When to make the switch

Microsoft retired the Bing Search APIs on August 11, 2025 and decommissioned their instances. If your application still expects the v7 result format, Search1API offers web, news and image search compatibility endpoints backed by its Bing engine.

Original service reference: Microsoft Bing Search API retirement notice

What you keep

Supported Bing v7 query parameters and result parsing.
The Ocp-Apim-Subscription-Key header, now carrying your Search1API key.
Configurable Open WebUI and LangChain Bing client integrations.

What to review before switching

Rankings and available metadata can differ from the retired API. Answers and additional response sections are not reproduced.
safeSearch, responseFilter, textDecorations and several other options are ignored. Review the parameter mapping if your application relies on them.
totalEstimatedMatches reflects the returned window, not an estimate of every match. News requires q; top-stories requests without a query are unavailable.

Move your existing client

Create a Search1API key to replace the Azure subscription key in your client.
Point the configurable Bing endpoint at /compat/bing/v7.0/search. Use the separate news or image path when needed.
Verify webPages.value parsing, filters, pagination and error handling with representative queries.

LangChain · BingSearchAPIWrapper — python
from langchain_community.utilities import BingSearchAPIWrapper
search = BingSearchAPIWrapper(
    bing_subscription_key="YOUR_SEARCH1API_KEY",
    bing_search_url="https://api.search1api.com/compat/bing/v7.0/search",
    k=5,
)
results = search.results("hono workers", 5)

Examples match the compatibility reference. Validate your own filters and result handling before switching production traffic.

Client examples:Open WebUI / LangChainRead the compatibility reference

Search uses your Search1API credits and account rate limit. Reading page content and selecting several engines can add charges; see the protocol reference for details.

View pricing

Migration questions

Do I need an Azure resource?

No. The compatible endpoint uses a Search1API key, credits and rate limits. It does not use your old Azure resource or revive the retired Microsoft service.

Are news and images supported?

Yes. The compatibility API has separate /v7.0/news/search and /v7.0/images/search endpoints. The reference explains their response fields and differences.

Does this cover every old Bing client?

A client must allow changing its endpoint and key. LangChain’s BingSearchAPIWrapper and Open WebUI’s request format were tested. Clients with a fixed Microsoft hostname need configuration support or a code change.

More migration guides

Search API migrations SearXNG Google Custom Search JSON API