Search result collection
Use Bing endpoints to turn search result collection into repeatable API requests with documented inputs and JSON responses.
Add Bing search data to ranking, discovery, and competitive intelligence pipelines.
Use Crawlora Bing endpoints for web search result collection and discovery workflows.
Endpoint families
1
Documented params
6
Examples
1
Live catalog snapshot
Active endpoints
1
Methods
GET
Required params
2
Schema refs
1
{
"platform": "Bing",
"endpoint": "bing-search",
"method": "GET",
"path": "/bing/search",
"auth": "apiKey"
}Use cases
Use Crawlora Bing endpoints for web search result collection and discovery workflows.
Use Bing endpoints to turn search result collection into repeatable API requests with documented inputs and JSON responses.
Use Bing endpoints to turn competitive discovery into repeatable API requests with documented inputs and JSON responses.
Use Bing endpoints to turn cross-engine comparisons into repeatable API requests with documented inputs and JSON responses.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/bing/search
Featured endpoints
/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 502 when Bing serves a challenge page or unusable HTML.
Related APIs
Start building