// request reference
Bing Search parameters
Send query parameters with GET /api/bing/search. Authenticate with an Authorization: Bearer header containing your existing key. Keep keys on your server, not in browser code.
The groups below list every request field, including compatibility restrictions. Read the extended reference for detailed types, defaults, parameter combinations and additional examples.
Search query
Send a Bing query and optional native display or date filters.
qRequired Bing query, up to 2,048 characters. Search operators are supported.
Example / input hint: pizza shops in New York
filtersNative Bing display or date filters, up to 8,192 characters with no controls.
Example / input hint: ex1:"ez5_20069_20433"
Search origin
Optionally provide a named location, coordinates, or both.
locationOptional city-level search origin, up to 256 characters.
Example / input hint: New York, New York
latOptional latitude from -90 through 90.
Example / input hint: 40.7128
lonOptional longitude from -180 through 180.
Example / input hint: -74.0060
Market & pagination
Choose at most one localization token and the native organic offset.
mktBing language-country market. Cannot be combined with cc.
Example / input hint: en-US
ccTwo-letter country of origin. Cannot be combined with mkt.
Example / input hint: US
firstOne-based organic offset, up to 9,007,199,254,740,991.
Example / input hint: 1
Content & device
Use bounded HTTP request profiles; no browser is started.
safeSearchBing adult-content setting. Input is normalized case-insensitively.
offmoderate moderate (default)strictdeviceSelects a desktop, tablet, or mobile HTTP user-agent profile.
desktop desktop (default)tabletmobile// response
Work with the complete JSON response
Response groups include organic_results, knowledge_graph, knowledge_graph_list, pagination, litescrape_pagination. Groups and fields depend on the upstream result.
The SDK examples use raise_for_error() or raiseForError() so API errors are not mistaken for successful results.