Bing Trends Scraper API: Turn Trend Pages Into Structured Data
Bing Trends pages are JavaScript-heavy and sit behind bot-detection layers, which makes a plain HTTP fetch unreliable.
This page explains how a managed scraping API handles the rendering, proxy rotation and bot checks so that a single request returns the trend data your pipeline needs — rising and breakout queries, search-volume deltas, related-query lists and regional breakdowns. It also maps each request control to the output it produces, distinguishes the three common failure modes, and gives a dated reference for plan limits.
What Bing Trends pages expose
A Bing Trends page carries several distinct data shapes, and it helps to know which one you actually need before choosing extraction logic:
- Rising and breakout queries — queries gaining momentum for a topic, useful for catching demand shifts before they show up in your own analytics.
- Search-volume deltas — how volume for a term or competitor set has moved over the trend window.
- Related-query lists — adjacent terms that co-occur with the seed query.
- Regional breakdowns — the same trend viewed per US state or per international market, which is the basis for regional campaign planning.
All four are available through the same endpoint; the difference is which controls you set and which fields you extract.
Request controls and what each one changes
The API takes a target URL plus optional parameters. The table below is a reader's map from control to effect, not a substitute for the full parameter reference.
| Control | What it does | When to reach for it |
|---|---|---|
render_js | Runs the page in a real headless browser and returns post-render HTML | Trend pages whose charts and query lists only appear after client-side JS executes |
country_code | Routes the request through a residential IP in the chosen country | Content that varies by geography, or regional trend comparison |
stealth_proxy | Applies premium proxy handling for tougher bot checks and CAPTCHAs | Pages that block ordinary rotating proxies |
extract_rules | CSS (or XPath) selectors mapped to field names; response returns parsed JSON | You know the page structure and want deterministic fields |
ai_extract_rules | A natural-language spec describing the fields you want; response returns parsed JSON | Page structure shifts often, or you want to describe fields in plain language |
screenshot | Captures a full-page screenshot | Visual QA of a trend page, or archiving a snapshot alongside the data |
A practical default for trend work is render_js on, country_code set to the market you care about, and one of the two extraction-rule families depending on how stable the page markup is.
Worked example: comparing a competitor term across two markets
Suppose you want to know whether a competitor's branded query is rising faster in one market than another. The sequence is:
- Build the Bing Trends URL for the competitor term.
- Send it twice — once with
country_codeset to the first market, once with the second — withrender_jsenabled so the trend chart and query lists are present in the response. - Attach
extract_rulesmapping the rising-query list and the volume-delta series to named fields, orai_extract_rulesif the markup is unstable. - Compare the two parsed JSON payloads field by field.
The value here is that the geo routing and the rendering happen inside the same request as the extraction, so the two market snapshots are collected under the same conditions rather than hours apart on differently configured local browsers.
Three failure modes that look alike but are not
When a trend request comes back empty or blocked, the cause is usually one of three things, and the fix differs each time:
- Your own concurrency ceiling. The API enforces concurrency limits per plan rather than per-target rate limits. If you fire more simultaneous requests than your plan allows, requests queue or fail regardless of the target. Fix: reduce parallelism or move to a higher-concurrency plan.
- Target-side throttling. Bing Trends itself may slow aggressive request patterns. Fix: space out requests or spread them across multiple sessions.
- Bot-detection blocking. The page returns a challenge instead of trend data. Fix: enable
stealth_proxyand confirmrender_jsis on so the page executes as a real browser would.
Separating these three before changing parameters saves a lot of trial and error.
From account to first parsed response
The workflow is short:
- Create an account to get an API key and starting credits.
- Install an SDK for your stack (Python, Node, Go, PHP, Ruby, Java) or use plain cURL — each scrape becomes a single call.
- Send the Bing Trends URL with your API key. The renderer executes the page in a real browser, rotates the IP, and returns a response your scraper can act on.
- Add advanced parameters as needed:
render_jsfor JavaScript,stealth_proxyfor CAPTCHAs,country_codefor geo-targeting,ai_extract_rulesfor natural-language extraction.
If you prefer not to write code at all, the dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in any of the supported languages.
Output formats
Depending on the controls you set, the response can be:
- Rendered HTML — the post-render page, ready for your own parser.
- Parsed JSON — produced by
extract_rules(selector-based) orai_extract_rules(natural-language spec). - Markdown — a clean, LLM-ready rendering of the page, useful when the trend text is going into a language model rather than a database.
- Screenshot — a full-page image for visual QA or archiving.
For a trend pipeline, parsed JSON is usually the right target; Markdown is a good fit when the downstream consumer is an LLM summarization step.
Plan reference: credits and concurrency
The table below reproduces the plan tiers, credit allowances and concurrency figures as captured on 2026-11-15. Treat it as a dated reference rather than a current price list — check the pricing page for today's numbers before committing.
Two things to read carefully in the table:
- Credits are monthly and do not roll over. A request starts at 1 credit; enabling JS rendering costs 5 credits per successful request, and premium proxies cost 10 or 25 credits depending on whether JS rendering is also on. A trend pipeline with
render_jsandstealth_proxyboth on therefore consumes credits much faster than the headline allowance suggests. - Concurrency is the real throughput ceiling. The credit column tells you monthly volume; the concurrency column tells you how many requests can be in flight at once. For a bursty trend-collection job, concurrency is usually the binding constraint.
All prices are exclusive of VAT. The plan table is delivered in full below.
Should you use a managed API for Bing Trends?
Use a managed scraping API when most of the following are true:
- [ ] You need trend data on a schedule and cannot afford silent gaps when bot checks change.
- [ ] You want geo-targeted collection (per-state or per-country) without maintaining your own residential proxy pool.
- [ ] You want parsed JSON or Markdown out of the box rather than maintaining a parser against shifting markup.
- [ ] Your volume fits within a plan's credit and concurrency envelope, or you can batch requests to stay under it.
Consider a self-hosted headless-browser stack instead when:
- [ ] Your volume is very low and occasional, so the fixed monthly cost outweighs the convenience.
- [ ] You already run a proxy pool and browser fleet for other targets.
- [ ] You need a data shape the extraction rules cannot express and would rather own the parser end to end.
A middle path: prototype in the dashboard request builder, confirm the fields you actually need, then decide whether the credit cost per successful request fits your budget.
| Plan | Price / month | API credits | Concurrent requests | JS rendering | Rotating & premium proxies | Geotargeting | Screenshots & extraction rules | Priority email support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|---|---|---|---|
| Hobby | $19 | 75,000 | 25 | Included | Included | Included | Included | Not included | Not included | Not included |
| Freelance | $49 | 250,000 | 50 | Included | Included | Included | Included | Not included | Not included | Not included |
| Startup (Recommended) | $99 | 1,000,000 | 100 | Included | Included | Included | Included | Not included | Not included | Not included |
| Business | $249 | 3,000,000 | 200 | Included | Included | Included | Included | Included | Included | Included |
| Business + | $599 | 8,000,000 | 400 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 14 | $999 | 14,000,000 | 500 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 24 | $1,599 | 24,000,000 | 600 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 | 41,000,000 | 700 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 69 | $3,599 | 69,000,000 | 800 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 120 | $5,799 | 120,000,000 | 900 | Included | Included | Included | Included | Included | Included | Included |
Dated reference captured 2026-11-15. Prices are exclusive of VAT. Credits are monthly and do not roll over; requests start at 1 credit, JS rendering costs 5 credits per successful request, premium proxies cost 10 or 25 credits depending on whether JS rendering is also enabled. Check current pricing before relying on these figures.
Frequently asked questions
Can I scrape Bing Trends without writing code?
Yes. The dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in Python, Node, Go, PHP, Ruby, or cURL.
How do I handle JavaScript when scraping Bing Trends?
Pass render_js=true on the request. The page runs in a real headless browser, the JavaScript executes server-side, and you receive the post-render HTML.
Can I scrape Bing Trends from a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This matters when trend content varies by geography.
What's the rate limit for scraping Bing Trends?
The API enforces concurrency limits per plan rather than per-target rate limits. If the target throttles aggressive patterns, space out requests or use multiple sessions.
How do I get structured JSON from Bing Trends?
You have two routes to a JSON payload. The first is extract_rules: you supply CSS selectors and pair each one with the field name it should populate, so the output shape is fixed by your own mapping. The second is ai_extract_rules: instead of selectors you describe the fields you want in ordinary language and let the extraction step interpret that description. Either way the API hands back parsed JSON rather than raw HTML, so the response can go straight into a trend pipeline.
Which programming languages can I use to scrape Bing Trends?
Any. SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java. Plain cURL works too, so you can stay with whatever your stack already uses.
How many credits does a single Bing Trends request cost?
A request starts at 1 credit. Enabling JS rendering costs 5 credits per successful request, and premium proxies cost 10 or 25 credits depending on whether JS rendering is also enabled. A trend request with both render_js and stealth_proxy on therefore costs more than the base rate — budget accordingly when sizing a plan.
Do credits roll over between months?
No. API credits are valid for one month and do not roll over, so unused allowance is not carried forward.