Search Bing

Response content format. md returns Markdown in data.content with data.format=md; the JSON success/request envelope remains. Accept: text/markdown also selects Markdown unless output or html=true is explicit. html is an alias for html=true and retains the existing Brotli/Base64 source format.

Select fields within data.content for JSON or Markdown. Supports comma-separated paths, non-negative array indices, half-open slices [0:3] (either bound may be omitted), [] and .{nested,subqueries}. Up to128 selections and16 levels. Missing fields are omitted; selected declared fields retain their zero defaults. The request envelope and credit headers remain. Include next_page_token when pagination is needed. Incompatible with HTML output. This changes response presentation only; tracing-enabled history retains the complete JSON result.

Accepted for compatibility. Searches are always fetched without a result cache for either value; normal successful-request billing applies.

The search query. The UTF-8 representation must not exceed 8,192 bytes; non-ASCII characters may use more than one byte.

Return Brotli-compressed, Base64-encoded source HTML instead of normalized JSON.

When true, PrismCrawl does not store the source HTML or parsed JSON. Audit and billing metadata is retained, but all other data is permanently discarded. Request history exposes only type ZERO_TRACE, the request HTTP status code, and whether the account was charged.

Search as a mobile, tablet, or desktop device.

Safe-search mode. active enables Google's filtering and Bing Strict SafeSearch; off requests unfiltered results. Search providers may still suppress content required by law or policy.

Request the provider's light or dark result-page theme. This affects source-page presentation, not ranking, and providers may ignore it.

Bing-native spelling hint. The supported value is -1, an undocumented field observed in Bing-generated search URLs. Its behavior is best-effort and may change upstream.

Bing's one-based native page position. Omit it or use 1 for the front page. Values greater than 1 require the next_page_token returned by the preceding response and must match that token; arbitrary offsets are rejected.

Opaque Bing continuation token from the preceding response, valid for one hour and the same account. When supplied, first may be omitted. Resend the same query, device, targeting, time range, and search controls. Restart pagination if the token is expired, rejected, or predates the authenticated-token rollout.

Two-letter Bing result-country code. Case-insensitive. The supported values follow Bing's published country-code list.

Named geographic search origin, resolved to coordinates. At most 512 UTF-8 bytes without control characters. Mutually exclusive with coordinates; resend the same name when paginating. Bing may also consider the query and other location signals.

Bing result market. Case-insensitive; mutually exclusive with cc. Resend it when paginating.

Native Bing filters copied from its search URL. At most 4096 UTF-8 bytes without control characters. Mutually exclusive with tbs; resend exactly when paginating.

Bing interface-language hint. It affects Bing-generated interface strings, such as related-search labels; it does not restrict search results to that language. Bing may fall back to English when it cannot localize a value. See Microsoft's current set_lang guidance.

Google-compatible time-range input translated to Bing's native date filter. Relative ranges use qdr:<unit>[amount], where the unit is d (day), w (week), m (month), or y (year), and the optional positive amount is at most 10,000. Custom inclusive ranges use cdr:1,cd_min:M/D/YYYY,cd_max:M/D/YYYY. Bing has day-level precision, so hour ranges (qdr:h) are rejected. Resend the same value with a filtered search's next_page_token.