Extract Bing search results, organic rankings, result URLs, snippets, related queries, news modules, video modules, and pagination metadata as structured JSON for rank monitoring.
Structured output
Use Crawlora's Bing Search API to collect public Bing SERP data without maintaining your own parser, proxy routing, retries, or response normalization layer. The endpoint returns structured JSON that can power SEO dashboards, keyword monitoring tools, competitor research, and AI search workflows.
SERP workflows
Bing search visibility can differ from Google, Brave, and other engines. Crawlora helps teams monitor where domains rank, which result modules appear, and how titles, URLs, and snippets change over time.
SERP monitoring workflowsRequest schema
These parameters come from the active Search Bing web results catalog entry.
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| q | string | Yes | Search query | openai |
| country | string | No | Two-letter country code; defaults to us | us |
| lang | string | No | Bing UI language; defaults to en-us | en-us |
| page | integer | No | 1-based page number; defaults to 1 | 1 |
| count | integer | No | Results per page; defaults to 10, clamped to 1..50 | 10 |
Example JSON
This example is rendered from the active endpoint catalog so the page stays aligned with Docs and Playground.
{
"code": 200,
"msg": "OK",
"data": {
"results": [
{
"position": 1,
"title": "OpenAI - Reddit",
"url": "https://www.reddit.com/r/OpenAI/",
"description": "OpenAI is an AI research and deployment company. OpenAI's mission is to ensure that artificial general intelligence benefits all of humanity...",
"hostname": "www.reddit.com",
"display_url": "https://www.reddit.com › OpenAI",
"favicon": "https://th.bing.com/th/id/ODLS.A2450BEC-5595-40BA-9F13-D9EC6AB74B9F..."
}
],
"pagination": {
"page": 1,
"count": 10,
"next_page": 2
}
}
}Endpoint catalog
/bing/searchReturns normalized Bing web search results for a query string, including organic results, optional context panel data, related queries, people-also-ask questions, news modules, video modules, and page-based pagination. Empty optional blocks are omitted from the JSON response. Locale defaults to country=us and lang=en-us. Results are fetched with the repo's Chrome-impersonated request client and return 503 when Bing serves a challenge page or unusable HTML.
/bing/newsReturns normalized Bing news search results for a query string. Locale defaults to country=us and lang=en-us. Results are fetched from public Bing news HTML/async pages and return 503 when Bing serves a challenge page or unusable HTML.
/bing/videosReturns normalized Bing video search results for a query string. Locale defaults to country=us and lang=en-us. Results are fetched from public Bing video HTML/async pages and return 503 when Bing serves a challenge page or unusable HTML.
/bing/imagesReturns normalized Bing image search results for a query string. Locale defaults to country=us and lang=en-us. Results are fetched from public Bing image HTML/async pages and return 503 when Bing serves a challenge page or unusable HTML.
/bing/suggestReturns Bing autosuggest query completions for a query prefix. Locale defaults to country=us and lang=en-us. Suggestions are fetched from public Bing suggest endpoints and trimmed to the requested count.
Managed execution
Crawlora wraps endpoint-specific request handling, proxy-aware collection, response parsing, and documented error behavior behind a stable API surface for supported public search result pages.
Endpoint-specific request logic for Bing web, news, video, image, and suggest pages
Proxy-aware collection and retry-aware execution where supported
Challenge-aware behavior for unusable upstream responses
Normalized JSON responses with Playground-tested examples
Credit-based usage tied to documented endpoint costs
Crawlora detects unusable upstream responses and returns documented errors instead of silently returning broken HTML.
Build or buy
Use this comparison to decide whether to maintain scraping infrastructure internally or call a managed endpoint.
| Requirement | Building internally | Crawlora |
|---|---|---|
| Proxy rotation | Buy, test, rotate, and monitor proxy pools. | Use managed proxy-aware collection where supported. |
| Parser maintenance | Maintain selectors as Bing layouts change. | Use endpoint-specific parsers maintained behind the API. |
| Schema normalization | Design and version your own response model. | Receive documented JSON fields from the catalog. |
| Retries and error classification | Classify challenges, empty pages, and upstream failures yourself. | Receive documented errors for unusable upstream responses. |
| Endpoint docs | Write and maintain internal API documentation. | Use generated Docs pages from the active endpoint catalog. |
| Playground testing | Build a test console for developers. | Test the same endpoint in Playground before shipping. |
| Usage billing | Create your own metering and limits. | Use credit-based usage and plan limits. |
| Monitoring | Instrument request volume and failures from scratch. | Use Crawlora's documented status and usage workflow. |
Crawlora is not the official Microsoft Bing Web Search API. Microsoft retired its Bing Search APIs on August 11, 2025, and the successor (Grounding with Bing Search in Azure AI Agents) is an Azure-hosted LLM grounding service, not a drop-in search API. Crawlora provides structured public web data extraction endpoints for supported Bing search result pages as a JSON alternative.
Related APIs
Connect this endpoint with adjacent Crawlora search, monitoring, docs, and pricing pages.
Compare Bing visibility with Google Search result data.
OpenAdd Brave Search results to cross-engine monitoring workflows.
OpenTrack keyword rankings, result changes, and search visibility.
OpenBuild keyword tracking dashboards from recurring search result snapshots.
OpenStore recurring SERP checks for keyword, URL, and competitor monitoring.
OpenCheck keyword positions and ranking URLs with structured Bing result snapshots.
OpenUse Crawlora as the data layer behind agency and SaaS SEO reports.
OpenPair SERP tracking with search demand and trend discovery.
OpenAfter Microsoft's August 2025 retirement: the alternatives and how to migrate to a JSON Bing search API.
OpenTurn Bing results into a rank tracker — record positions, URLs, and snippets over time.
OpenReview plans, credits, limits, and usage options.
OpenFAQ
Answers for developers evaluating Crawlora for supported public search result pages.
Yes. Crawlora provides a Bing Search endpoint for supported public Bing search result pages and returns normalized JSON through documented API routes.
Yes. Teams use the Bing Search API as a Bing API for rankings: each response includes organic result positions, titles, URLs, snippets, and pagination context, so you can record keyword rankings over time and detect SERP changes. Pair recurring snapshots with the SERP monitoring use case to build a Bing rank tracker.
The catalog example includes organic results with positions, titles, URLs, descriptions, hostnames, display URLs, favicon data, and pagination metadata. Optional related queries, people-also-ask, news, video, and context modules can appear when Bing includes them.
The Bing Search API parameters are q (query), country, lang, page, and count. Country and language localize results so you can rank-track across markets.
Yes. The Bing platform includes search, news, videos, images, and suggest endpoints where they are active in the generated catalog.
Crawlora detects unusable upstream responses and returns documented errors instead of silently returning broken HTML. Current Bing endpoint docs list upstream failures as 503 responses.
Yes. Microsoft deprecated and retired the Bing Search APIs on August 11, 2025 — existing keys now return HTTP 410, and the official successor (Grounding with Bing Search in Azure AI Agents) is an Azure-hosted LLM grounding service rather than a drop-in search API. Crawlora's Bing Search endpoint is an alternative that returns Bing web, news, video, image, and suggestion results as normalized JSON.
Microsoft no longer issues Bing Search API keys after the August 2025 retirement. With Crawlora you use a single Crawlora API key (sent as the x-api-key header) to call the Bing Search endpoint — there is no separate Microsoft or Azure key to provision.
No. Crawlora is not the official Microsoft Bing Web Search API. Microsoft retired its Bing Search APIs on August 11, 2025, so there is no longer a first-party Bing Search API to sign up for. Crawlora provides structured public web data extraction endpoints for supported Bing search result pages as a JSON alternative.
Test /bing/search in Playground, inspect the current response schema in Docs, and compare credit-based usage on the pricing page.