Press releases are a real-time feed of corporate news — product launches, earnings, partnerships, executive moves. But PR Newswire is built for reading, not for ingesting: there is no clean feed to pull releases (with headlines, tickers, and full body text) into a monitoring workflow.
This guide shows how to collect press releases as structured JSON, on demand or on a schedule.
Who uses press-release data
Several teams rely on a structured press-release feed. Investor-relations and communications teams monitor how peers announce news and time their own releases. Market and competitive-intelligence analysts watch for launches, partnerships, and executive changes across a sector. Media-monitoring and PR agencies track coverage and mentions for clients. And data teams feed the releases into dashboards or alerting so that material corporate news reaches the right people without anyone refreshing a website.
What the data looks like
One record per release. A real row from a live run:
| Field | Example |
|---|---|
| title | Das Golden Melody Festival 2026 ging erfolgreich zu Ende |
| time_label | Jul 01, 2026, 23:36 ET |
| url | prnewswire.com/news-releases/… |
| image_url | mma.prnewswire.com/media/… |
| tickers | [] |
Records also include the summary, full body text (optional), category, and country, so you can filter by topic or ticker.
How to get it
Run the PR Newswire Scraper on Apify with a keyword or category. Output is JSON, CSV, or Excel, priced per release.
Run it on a schedule
For monitoring, schedule a weekday run (Schedules → Add schedule) with input like:
{
"keyword": "your topic or company",
"country": "US",
"maxReleases": 50,
"includeFullBody": false
}Common workflows
The typical jobs are: a keyword watch that pulls every release mentioning a company or topic on a schedule; a sector sweep that collects releases in a category to summarise the week’s news; a ticker filter that routes releases referencing specific symbols into a finance workflow; and an archive build that stores full body text for later search and analysis. Because the output is clean JSON or CSV, each of these plugs straight into a spreadsheet, a database, or a downstream summariser.
Why pull it as structured data
Press-release sites are designed for human reading, not ingestion. Copying headlines, dates, tickers, and body text by hand does not scale, and generic RSS feeds drop most of the useful fields. Collecting releases as structured records keeps every field you need — title, timestamp, tickers, category, and full text — in a form you can filter, store, and analyse.
From feed to newsroom-grade monitoring
A structured release feed becomes far more useful once it runs on a schedule and lands somewhere searchable. Point a keyword or category job at a recurring run, deliver the output to a store your team already checks, and you have continuous monitoring: new releases arrive automatically, each one carrying its title, timestamp, category, any tickers, and full text. From there you can summarise the day’s news, flag releases that mention a competitor or a portfolio company, and keep a searchable archive that grows on its own. Because you control the keywords and cadence, the feed stays focused on what matters to you rather than the firehose of everything published.
Best practices
Keep separate scheduled jobs per topic so feeds stay clean and independently routable, cap results while you validate the fields, and only enable full body text when you actually need it — each release is billed per record, so scoping the run keeps cost predictable and the output tidy.
Cost and control
Pricing is per release returned, with no subscription, so the cost of a run tracks exactly how many releases match your keyword or category. A focused daily watch on one company returns a few releases for a few cents; a broad weekly sector sweep returns more and costs proportionally more. You set the cap and the cadence, and a run that finds nothing new costs only the tiny start fee — which is what makes continuous monitoring affordable rather than a budget line.
FAQ
Can I filter by ticker or topic? Yes — search by keyword or category, and each record carries any tickers referenced.
Can I get the full release text? Yes, enable full body in the input (each release is billed per record).
How fresh is it? It reads the latest published releases at run time; schedule it to keep a rolling feed.
Can I archive the full text? Yes — enable full body in the input and each release is stored with its complete text, billed per record.
Can I run several keyword watches? Yes — schedule one job per keyword or category so each feed stays clean and separately routable.
Can an AI agent run it? Yes — it is Pay-Per-Event, so agents can call it via Apify’s x402 support and pay per run in USDC, no account required.
Related: Startup Funding Tracker and Google Trends Scraper for market-intelligence workflows.
See also: New β PR TIMES Scraper β Japan Press Releases Β· γγ¬γΉγͺγͺγΌγΉ API
We cover AI agents, automation, and the tools that make them work. Our mission is to make AI accessible to everyone.