Economic News Scraper API
Economic-news sites are a hostile place to run a homegrown scraper: paywalls, consent walls, rotating ad stacks and JavaScript-rendered article bodies all change the shape of the page you thought you were parsing.
This page describes a managed request layer that takes a public article URL, renders it, rotates proxies and returns either the rendered HTML or a structured payload you define. Use it to decide whether that trade-off fits your collection job, and to see exactly which request options change the output and the credit cost.
What this API does
You send one GET request containing the article URL and your API key. The service renders the page in a headless browser, rotates residential proxies, deals with bot detection, and hands back rendered HTML that is ready to parse. You are not running Chrome, not maintaining a proxy pool, and not writing per-site bypass logic.
For economic-news article pages specifically, the fields that typically matter are the headline, byline, publish timestamp, source publication, summary, body copy, article URL and the entity tags the outlet attaches (companies, indices, indicators). Those are the fields the service is designed to return, either as raw HTML or as structured output you define through extraction rules.
Three collection patterns
Most teams arrive with one of three jobs in mind, and the request shape is the same for all of them:
- Economic data trends. Collect article pages that discuss releases, revisions and forecasts so you can position, spot growth areas and adjust strategy.
- Market sentiment signals. Pull sentiment-oriented coverage to compare against competitors, track how the narrative moves and feed strategic decisions.
- Commodity price shifts. Track coverage of commodity moves over time to support investment analysis and risk management.
In each case the unit of work is a public article URL. The difference is downstream: what you extract and how often you re-run the collection.
Request controls and what each one changes
The advanced parameters are the part most teams get wrong on the first pass, because each one changes both the output and the credit cost. Map them before you build:
- render_js — turns on JavaScript rendering. Needed when the article body or metadata only appears after scripts run. Costs 5 credits per successful request.
- stealth_proxy — the heaviest proxy tier, used when a site actively challenges automated traffic. Costs 75 credits per request.
- country_code — routes the request through a chosen country or territory, useful when an outlet serves different content or consent behaviour by region.
- extract_rules — CSS or XPath selectors mapped to field names, returning structured JSON instead of raw HTML.
- ai_extract_rules — a natural-language specification of the fields you want, for pages where writing selectors is fragile.
Start with the cheapest configuration that returns the fields you need, then add tiers only when a specific site fails.
Credit cost per request
Credits are consumed per successful request and the amount depends on which options are enabled. The supplied figures are: 5 credits for JS rendering, 25 for premium_proxy combined with JS rendering, and 75 for stealth_proxy. API credits are valid for one month and do not roll over; requests start at 1 credit each.
A worked example using those figures: a batch of 1,000 article pages rendered with JavaScript at 5 credits each consumes 5,000 credits. The same batch routed through stealth_proxy at 75 credits each consumes 75,000 credits — the entire Hobby plan allowance. That gap is the reason to test the cheapest configuration that works on each target site before scaling a run.
Plan tiers and their allowances are listed in the pricing table below; treat the figures as reference values to confirm against current plans before committing budget.
Choosing an extraction approach
There are three sensible outputs, and the right one depends on how stable the target site is:
- Raw rendered HTML. Cheapest and most flexible. Choose this when you already have a parser, when you need fields you have not defined yet, or when you are still exploring a new outlet.
- CSS/XPath extraction rules. Choose this when the article template is stable and you know the field names you want. It returns parsed JSON and removes a parsing step from your pipeline.
- AI extraction rules. Choose this when selectors break often, when the outlet changes markup, or when the field you want is described more easily in words than in a selector. It is the most forgiving option and the one to reach for when maintenance cost, not credit cost, is the constraint.
A practical rule: prototype with raw HTML, promote to CSS/XPath once the template settles, and keep AI extraction as the fallback for the outlets that keep breaking your selectors.
Legal and scope pre-flight
Before you deploy, run this short checklist:
- Confirm the target pages are public-facing and not behind a login.
- Read the outlet's terms of service and confirm that automated collection is permitted for your use.
- Confirm you are not collecting personal data you do not need; the service does not store personal data from scraped sites unless you explicitly request it.
- Decide your retention policy for article bodies and bylines before the first run, not after.
If any of those checks fails, the right answer is a licensed feed or a direct data agreement, not a scraper.
Setup path
- Create an account to get an API key and the free starting credits.
- Install the SDK for your stack — Python, Node.js, Go, PHP, Ruby or Java — or use plain cURL. Code samples exist for each, and the dashboard has a request builder for testing without writing code.
- Send a GET request with your API key and a public economic-news article URL.
- Add advanced parameters only as needed: render_js, stealth_proxy, country_code, extract_rules or ai_extract_rules.
Setup is designed to take minutes, not days; the request builder is the fastest way to confirm a target site returns the fields you expect before you wire it into a pipeline.
Failure triage
When a run returns something unexpected, the cause is usually one of three things, and they need different fixes:
- Blocked or empty render. The page came back without the article body. This is a rendering or anti-bot problem: raise the proxy tier, enable render_js, or set a country_code that matches the outlet's regional behaviour.
- Wrong extraction rule. The page rendered but the JSON fields are empty or mismatched. This is a selector problem: check the CSS/XPath against the current markup, or switch to ai_extract_rules while you re-derive the selectors.
- Legal or terms-of-service problem. The request succeeds but you should not be making it. This is not a technical failure and no parameter fixes it; revisit the pre-flight checklist and confirm the page is public and permitted.
Separating these three early saves the most time, because the first two are configuration changes and the third is a scope decision.
Frequently asked questions
Do I need an account to scrape economic news?
You need an API key from the provider, but not an account on the news site itself. Sign-up includes 1,000 free credits and no card is required. After that, you send the article URL and the service handles rendering and proxies.
Is scraping economic news legal?
Public-facing pages can usually be collected, but check the target site's terms of service before you deploy and stay away from content behind a login.
What data can I extract from economic news?
Anything that renders on the public page. You can use extract_rules with CSS selectors, or ai_extract_rules for AI-driven extraction, and get structured JSON back.
How do I get structured JSON from economic news?
You have two routes. Define extract_rules as a map of field names to CSS selectors, or describe the fields you want in plain language with ai_extract_rules. Either way, the response arrives as parsed JSON rather than raw HTML.
Which programming languages can I use to scrape economic news?
Any. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too. Use whatever your stack already runs.
How much does it cost to scrape economic news?
Sign-up includes 1,000 free credits with no card. Paid plans start at $19/month for higher volume and concurrency. Per-request credit cost depends on options: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy.