Bing Scraper API alternatives
Most teams comparing Bing Scraper API alternatives are working around the same fact: Microsoft is winding down the Bing Web Search API in Azure, and it was closed to new customers in 2023. This page lays out the real options side by side, the sunsetting official API, SerpApi's Bing engine, and the Oxylabs, Bright Data, and ScrapingBee Bing scrapers, and our own, so you can pick the one that fits your job and your budget.
How it compares
| Option | Setup | Bing coverage | Parsing | Pricing model | Free tier |
|---|---|---|---|---|---|
| bingscraperapi | one API key | search, images, videos, recipes | parsed JSON | Pay per successful request | 1,000 requests |
| Bing Web Search API (Azure) | Azure account + resource | web, images, video, news | JSON, but retiring | Tiered, being sunset | closed to new customers |
| SerpApi (Bing engine) | API key | Bing SERP + blocks | parsed JSON | Subscription by searches | limited free searches |
| Oxylabs Bing Scraper | enterprise scraper API contract | SERP via scraper | parse it yourself | Subscription, higher entry tier | trial on request |
| Bright Data Bing Scraper | account + proxy or dataset setup | SERP via scraper | parse it yourself | Pay per record / subscription | trial credits on signup |
| ScrapingBee Bing Scraper | you write the parser | SERP via scraper | parse it yourself | Credits / subscription | 1,000 trial credits |
Quickstart
curl "https://api.bingscraperapi.com/api/v1/bing/search?q=how+tall+is+mount+everest&api_key=$API_KEY"import requests, os
# One real API call: query in, ranked Bing organic results out as JSON.
resp = requests.get(
"https://api.bingscraperapi.com/api/v1/bing/search",
params={
"q": "how tall is mount everest",
"api_key": os.environ["API_KEY"],
},
timeout=30,
)
data = resp.json()
print(data["results_count"], "organic results")
for r in data["organic_results"]:
print(r["position"], r["title"], r["link"])Response
{
"query": "how tall is mount everest",
"engine": "bing",
"results_count": 8,
"organic_results": [
{
"position": 1,
"title": "Mount Everest | Height, Map, Deaths, Facts, & Climbers | Britannica",
"link": "https://www.britannica.com/place/Mount-Everest",
"displayed_link": "https://www.britannica.com › place › Mount-Everest",
"snippet": null,
"date": null,
"source": "bing"
}
],
"answer_box": {
"type": "answer",
"answer": "8,849 m / 29,032 ft",
"title": "Deep dive into how tall is mount eve…"
}
}Use it for
You need a long-term route to Bing data
You want one general SERP API
You already pay Oxylabs, Bright Data, or ScrapingBee
You need images, videos, or recipes too
How it works
- Send a GET request with your target and API key.
- We route through residential proxies, handle anti-bot, and parse the response.
- You get validated JSON back, ready to use.
Pricing
| Plan | Price | Best for |
|---|---|---|
| Free | 1,000 requests | Testing and small jobs |
| Pro | $0.60 / 1k | Production workloads |
| Pay-as-you-go | $0.90 / 1k | Spiky or one-off volume |
Median response 2.6s. You only pay for successful requests.
FAQ
Is there an official Bing search API?
There was, but it is going away. The Bing Web Search API in Azure Cognitive Services was closed to new customers in October 2023, and Microsoft has been retiring the service. Existing customers were given a wind-down window, but it is not a route new projects can rely on. That is why most teams building on Bing today use a scraper API that reads the live public SERP, such as ours, which returns the results as clean JSON.
What is the best Bing Scraper API?
The best Bing Scraper API depends on the job. If you already run a general SERP API like SerpApi across several engines, adding its Bing engine is convenient. If you want Bing-focused endpoints for search, images, videos, and recipes under one key with success-only billing, a dedicated API like ours fits better. If you are an enterprise with an existing Oxylabs, Bright Data, or ScrapingBee contract, pointing that at Bing avoids a new vendor, at the cost of parsing the fields yourself.
Why use a Bing Scraper API instead of the official API?
Because the official Bing Web Search API is closed to new customers and being retired, so it is not available for new projects and is a risk for existing ones. A Bing Scraper API reads what a logged-out visitor sees on the live SERP and returns it as JSON, authenticates with a single key, and is maintained against Bing's markup. The trade-off is the billing model: you pay per request rather than through an Azure subscription.
How does SerpApi compare for Bing?
SerpApi is a capable general SERP API that supports Bing among many engines and returns parsed JSON with SERP blocks, billed by searches on a subscription with a small free allowance. Our API is Bing-specific with dedicated endpoints for search, images, videos, and recipes, success-only billing, and a 1,000-request free tier. If you only target Bing, the focused API is usually the better value; if you need many engines from one vendor, SerpApi is worth a look.
How do the Oxylabs, Bright Data, and ScrapingBee Bing scrapers compare?
The Oxylabs, Bright Data, and ScrapingBee Bing scrapers are all capable, but they are general scraping platforms priced for enterprise volume, and most of them hand back raw HTML or a generic page payload you still parse into Bing fields yourself. Our API is Bing-specific: organic results, images, videos, and recipes each come from a dedicated endpoint as parsed JSON, billed per successful request, with a 1,000-request free tier to test before you commit.
Do I need proxies or an Azure account to scrape Bing?
It depends on the route. The retiring official API needed an Azure account but no proxies, while a do-it-yourself scraper needs your own proxy pool and breaks when Bing blocks datacenter IPs or serves a consent shell. Our Bing Scraper API needs neither: proxy rotation, anti-bot handling, and retries run on our servers, and you send one request with your API key. The free tier includes 1,000 requests to test it.