Skip to content

Collect PR Newswire Releases Through One API Call

PR Newswire publishes a steady stream of corporate announcements, and teams that track those releases usually need three things: a reliable way to fetch pages, a predictable way to extract fields, and a clear cost model.

OUTPUT FORMATSHTMLJSONMarkdown

This guide maps the request controls, credit rules, and output fields for a managed PR Newswire scraping workflow so you can decide whether it fits your pipeline before you write code.

What teams collect from PR Newswire

Most PR Newswire collection work falls into three jobs. The first is monitoring the wire for releases tagged with the industries, companies, or topics you follow, which feeds competitive-intelligence pipelines and PR-monitoring dashboards. The second is gathering press release data for trend analysis, partnership discovery, and strategic positioning. The third is pulling corporate contact details where they are exposed, which supports lead generation and outreach planning.

A release page typically returns headline, body copy, company tags, industry tags, distribution tier, publication timestamp, and contact details where the page exposes them. If a field is not rendered on the public page, the API cannot return it, so confirm the target page actually shows the data you need before building extraction rules around it.

Request controls and what they change

The API accepts a PR Newswire URL plus your extraction logic. JavaScript rendering, proxy rotation, and bot-detection handling happen behind the scenes, and you receive structured output.

Use this field map to choose controls before you send a request:

  • render_js=true runs the page in a real headless browser, executes JavaScript server-side, and returns post-render HTML. Use it when release content or tags load after the initial document.
  • stealth_proxy enables a stealth proxy for targets that respond aggressively to automated traffic.
  • country_code routes the request through a residential IP in the specified country, which matters when content varies by geography.
  • extract_rules accepts CSS selectors for structured extraction; ai_extract_rules accepts natural-language extraction instructions and returns structured JSON.
  • Screenshots and full-page capture are available when you need a visual record of a release page.

A request builder in the dashboard lets you paste a URL, set parameters, and copy a generated snippet in Python, Node, Go, PHP, Ruby, or cURL, so you can start without writing the request from scratch.

Credit costs and plan capacity

API credits are valid for one month and do not roll over. A standard request starts at 1 credit. Enabling JavaScript rendering raises a successful request to 5 credits. Enabling premium proxies costs 10 credits when JavaScript rendering is disabled, or 25 credits when it is enabled. Concurrent requests are the number of requests that can be sent at the same time.

The pricing table below lists every plan, its monthly price, credit allowance, concurrency limit, and feature availability exactly as published. Prices are exclusive of VAT. Treat the figures as a dated reference and check current pricing before you commit to a plan.

Worked example: estimating a monthly budget

Suppose you monitor 500 release pages per month and each page needs JavaScript rendering but not premium proxies. At 5 credits per successful rendered request, that workload consumes 2,500 credits. The Hobby plan includes 75,000 credits per month, so this workload fits comfortably within that allowance. If you also enable premium proxies with JavaScript rendering on every request, the cost becomes 25 credits per request, or 12,500 credits for the same 500 pages, which still fits within the Hobby allowance but leaves less headroom for other jobs.

This example uses only the published credit rules and plan allowances. It does not account for failed requests, retries, or additional pages you may fetch during development.

Blocking versus rendering: a useful distinction

Two failure modes look similar but need different fixes. If a request returns a challenge page, a CAPTCHA, or an access-denied response, the target is treating your traffic as automated. Proxy rotation and a real headless browser reduce that risk, and enabling stealth_proxy is the next step when a target responds aggressively. If a request returns HTML that is missing release body copy or tags, the page likely loads that content with JavaScript after the initial document. In that case, set render_js=true so the API executes the page in a real browser and returns the post-render HTML.

Checking the response body before changing controls saves credits. A challenge page and an incomplete render both look like missing data, but only one of them is solved by rendering.

Getting started

Create an account to get an API key and free test credits. Install the Python SDK or use the Node, Go, PHP, or Ruby client, or send a GET request with the target URL. The API renders the page, rotates proxies, and returns the data. Documentation includes examples in Python, Node.js, cURL, and a request builder, so you can copy a snippet, swap in your API key, and send the request.

Plan pricing and capacity
PlanMonthly priceAPI creditsConcurrent requestsJavaScript renderingRotating & premium proxiesGeotargetingScreenshots & extraction rulesPriority email supportDedicated account managerTeam management
Hobby$19 /mo75,00025IncludedIncludedIncludedIncludedNot includedNot includedNot included
Freelance$49 /mo250,00050IncludedIncludedIncludedIncludedNot includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100IncludedIncludedIncludedIncludedNot includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncludedIncludedIncludedIncludedIncluded

Prices are exclusive of VAT. API credits are valid for one month and do not roll over. Requests start at 1 credit each. Figures are a dated reference; check current pricing before purchase.

Frequently asked questions

What data can I extract from PR Newswire?

You can capture any field that appears on the public release page. Point extract_rules at elements with CSS selectors, or describe the fields you want in plain language with ai_extract_rules and receive structured JSON in return. Release pages commonly expose headline, body copy, company tags, industry tags, distribution tier, publication timestamp, and contact details where shown.

How do I get started scraping PR Newswire?

Sign up, grab your API key, and send a GET request with the target URL. The API renders the page, rotates proxies, and returns the data. Free test credits are available to try the workflow.

Will I get blocked when scraping PR Newswire?

Requests are routed through rotating residential proxies and a genuine headless browser, so they resemble ordinary visitor traffic. When a target tightens its defenses, add stealth_proxy to the request.

Can I scrape PR Newswire without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby, or cURL.

How do I handle JavaScript when scraping PR Newswire?

Pass render_js=true on the request. The API runs the page in a real headless browser, executes the JavaScript server-side, and returns the post-render HTML.

Can I scrape PR Newswire from a specific country?

Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when content varies by geography.