Bing Scraper API
Turn live Bing pages into structured JSON over one REST API. Organic results, images, videos, and recipes, each from a dedicated endpoint, plus SERP blocks like the answer box and related searches on the search call, with every link decoded and the market pinned for you.
Free 1,000 requests. Median response 2.6s. Market pinned to en-US. No Azure account, no credit card.
curl "https://api.bingscraperapi.com/api/v1/bing/search?q=web+scraping&api_key=$API_KEY" Scrape Bing without getting blocked
Anti-bot bypass
Proxy rotation
JS rendering
Structured JSON
Pay for success
One REST call
Choose from multiple Bing Scraper API endpoints
Related Searches & Questions
Knowledge Graph & Answer Box
Organic Results
Images
Ads Results
Videos
Recipes Results
Maps
What you can build
Rank tracking on Bing
SERP feature monitoring
Ads and competitive research
Image and video sourcing
Recipe and content aggregation
Keyword expansion
Simple, usage-based pricing
- All endpoints included
- Structured JSON output
- Anti-bot + rotating proxies
- 10 concurrent requests
- Community support
- Everything in Free
- Higher concurrency
- Email support
- Everything in Vibe
- Priority request routing
- Priority support
- Everything in Pro
- 500+ concurrent requests
- SLA + dedicated support
Pay-as-you-go top-ups run $0.90 per 1,000 successful requests. Median response 2.6s. You only pay for requests that succeed.
Drops into your stack
No-code
LLM and RAG
SDKs and REST
FAQ
A Bing Scraper API is a REST service that reads live public Bing pages and returns them as structured JSON. Ours covers the surfaces Bing renders to a logged-out visitor: organic search results, images, videos, and recipes, each from a dedicated endpoint. You send one GET request with an api_key and get parsed JSON back, with every result link decoded and the market pinned so the data is reproducible.
Not a dependable one anymore. Microsoft closed the Bing Web Search API in Azure Cognitive Services to new customers in October 2023 and has been retiring the service, so it is not a route new projects can build on. That is why teams use a Bing Scraper API that reads the live public SERP instead, which is what ours does, returning the results as clean JSON with no Azure account.
Scraping publicly visible search results is generally treated as lower risk than scraping data behind a login, and US courts have repeatedly found that accessing public web data does not by itself violate the Computer Fraud and Abuse Act. This is general information, not legal advice: you remain responsible for respecting Bing's terms, for copyright, for personal-data rules such as the GDPR, and for the laws in your jurisdiction. Use the API for aggregate SERP research rather than republishing content wholesale.
Four public surfaces, each with a dedicated endpoint: organic search results, images, videos, and recipes. The search endpoint also attaches SERP blocks, the answer box, related searches, related questions, ads, and knowledge graph, whenever Bing server-renders them. Every endpoint accepts a query, returns the same structured JSON style, and shares one api_key and the 1,000-request free tier.
Bing wraps result, ad, and entity links in a bing.com/ck/a redirect with the real URL base64url-encoded inside. Our scraper decodes that payload on every link and returns the real destination URL, so you never parse or follow the redirect yourself. Undecodable redirects are dropped rather than returned as bing.com links.
The free plan covers 1,000 requests with no card. Pro works out to about $0.60 per 1,000 requests and pay-as-you-go is $0.90 per 1,000, and you are billed only for successful requests. Retries across proxy tiers behind a successful call are not charged separately.