📰 Press-Release Event Feed — Official Newsroom Watch avatar

📰 Press-Release Event Feed — Official Newsroom Watch

Pricing

from $10.05 / 1,000 press-release deltas

Go to Apify Store
📰 Press-Release Event Feed — Official Newsroom Watch

📰 Press-Release Event Feed — Official Newsroom Watch

One deduped press-release event feed from buyer-supplied official newsroom feeds, with confirmed cross-feed deltas. No licensed wires.

Pricing

from $10.05 / 1,000 press-release deltas

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

📣 📰 Press-Release Event Feed — Official Newsroom Watch

Monitor selected public official newsrooms and receive only new, updated, or confirmed retracted release records after the seed run.

Output is one press_release_record row per result; billing is pay-per-event, the value event being one press-release delta (a $0.02 start fee per run, then $0.01 per press-release delta plus one $0.10 source check per run that reads the source).

7. Use with:

Communications teams tracking official announcements; compliance teams monitoring regulator releases; investors collecting dated public-company records; researchers maintaining reproducible event corpora; agencies serving multi-client newsroom watches.

📊 Sample Output

📰 Press-Release Event Feed — Official Newsroom Watch sample output — a table of real press-release delta rows (run_id, publisher, source_feed_url, release_id) from run h1kKeLkA8O37Abdfy on build 0.1.20

Real rows from run h1kKeLkA8O37Abdfy on build 0.1.20 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

run_idpublishersource_feed_urlrelease_idcomposite_keypublished_at
h1kKeLkA8O37AbdfyU.S. Securities and Exchange Commissionhttps://www.sec.gov/news/pressreleases.rss29d9b3fa-0eed-432e-850c-0978c0f4c49bsec.gov|29d9b3fa-0eed-432e-850c-0978c0f4c49bThu, 17 Sep 2026 08:55:00 -0400
h1kKeLkA8O37AbdfyU.S. Securities and Exchange Commissionhttps://www.sec.gov/news/pressreleases.rssb3074906-964e-4cc4-81f3-1162a1036f7esec.gov|b3074906-964e-4cc4-81f3-1162a1036f7eWed, 16 Sep 2026 10:00:00 -0400
h1kKeLkA8O37AbdfyU.S. Securities and Exchange Commissionhttps://www.sec.gov/news/pressreleases.rsse311a18a-b7e8-4bad-8c06-c8e60e484bccsec.gov|e311a18a-b7e8-4bad-8c06-c8e60e484bccMon, 14 Sep 2026 12:47:00 -0400
h1kKeLkA8O37AbdfyU.S. Securities and Exchange Commissionhttps://www.sec.gov/news/pressreleases.rss937571b2-423b-4228-905f-4034e7af3766sec.gov|937571b2-423b-4228-905f-4034e7af3766Fri, 11 Sep 2026 11:00:00 -0400
h1kKeLkA8O37AbdfyU.S. Securities and Exchange Commissionhttps://www.sec.gov/news/pressreleases.rssc2889ff5-77c4-4858-b5ae-e2b94d15998esec.gov|c2889ff5-77c4-4858-b5ae-e2b94d15998eThu, 10 Sep 2026 13:45:22 -0400
h1kKeLkA8O37AbdfyU.S. Securities and Exchange Commissionhttps://www.sec.gov/news/pressreleases.rss06cec215-1a77-4ef5-826d-4a0a23404513sec.gov|06cec215-1a77-4ef5-826d-4a0a23404513Thu, 03 Sep 2026 16:30:00 -0400
h1kKeLkA8O37AbdfyU.S. Securities and Exchange Commissionhttps://www.sec.gov/news/pressreleases.rss7b964f5e-d7e8-41ff-9d1a-c1bf94e8ca11sec.gov|7b964f5e-d7e8-41ff-9d1a-c1bf94e8ca11Thu, 03 Sep 2026 10:27:49 -0400
h1kKeLkA8O37AbdfyU.S. Securities and Exchange Commissionhttps://www.sec.gov/news/pressreleases.rss520b1092-2fa4-4ecd-ac8c-f5b43146f5bfsec.gov|520b1092-2fa4-4ecd-ac8c-f5b43146f5bfTue, 01 Sep 2026 15:17:39 -0400

The run finished with the status message: NORMAL: records=25; sources_complete=1/1

✅ What you get

One of three record types, discriminated by record_type: press_release_record, press_release_delta, or source_receipt.

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

  • record_type (string) — Discriminator.
  • run_id (string) — Apify run id that produced this item.
  • publisher (string/null) — Publishing organization label.
  • jurisdiction (string/null) — ISO 3166-1 alpha-2, EU, or GLOBAL.
  • source_feed_url (string/null) — Configured feed/listing URL for this source.
  • release_id (string/null) — Native GUID/id, else SHA-256 of the canonical URL.
  • composite_key (string/null) — lowercase registrable publisher domain|release_id.
  • title (string/null) — Release headline (non-null on press_release_record).
  • canonical_url (string/null) — Canonical public release URL (non-null on press_release_record).
  • published_at (string/null) — Publisher-stated publication time (may be null).
  • updated_at (string/null) — Publisher-stated update time (may be null).
  • authors (array/null) — Release authors.
  • categories (array/null) — Release categories/tags.
  • language (string/null) — BCP-47 language tag when known.
  • summary (string/null) — Normalized release summary.
  • body_text (string/null) — Normalized article body (only when includeArticleText).
  • body_truncated (boolean/null) — Whether the body_text was truncated at the cap.
  • attachments (array/null) — Release attachments: url, title, mime_type.
  • source_url (string) — Exact public request URL supporting this item.
  • observed_at (string) — RFC3339 UTC time after shape validation.
  • content_hash (string/null) — SHA-256 over canonical buyer-visible mutable fields.
  • delta_type (string/null) — press_release_delta only.
  • changed_fields (array/null) — Sorted changed field names on an updated_release delta.
  • absence_confirmations (integer/null) — Consecutive confirmed-gone runs behind a retraction.
  • terminal (string/null) — source_receipt only.
  • reason_code (string/null) — Stable terminal reason code.
  • canary_passed (boolean/null) — Whether the source-shape canary passed for this source.

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
"sources": [
{
"publisher": "U.S. Securities and Exchange Commission",
"url": "https://www.sec.gov/news/pressreleases.rss",
"format": "rss"
}
],
"watchMode": false,
"includeArticleText": false,
"maxItems": 25,
"maxRequests": 25,
"maxConcurrency": 3
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 25 × $0.005 press-release-record + 0 × $0.01 press-release-delta + 1 × $0.10 source-check = $0.24 on the Free tier — snapshot preview rows are delivered unbilled; only the source check and the start fee were charged.

2. A smaller, narrowed run

{
"sources": [
{
"publisher": "U.S. Securities and Exchange Commission",
"url": "https://www.sec.gov/news/pressreleases.rss",
"format": "rss"
}
],
"watchMode": false,
"includeArticleText": false,
"maxItems": 5,
"maxRequests": 25,
"maxConcurrency": 3
}

Caps the run at 5 rows; same billing shape as the sample run above.

3. Watch mode on a schedule

{
"sources": [
{
"publisher": "U.S. Securities and Exchange Commission",
"url": "https://www.sec.gov/news/pressreleases.rss",
"format": "rss"
}
],
"watchMode": true,
"includeArticleText": false,
"maxItems": 25,
"maxRequests": 25,
"maxConcurrency": 3
}

The first run seeds a private baseline and emits zero deltas; every later run emits one row per change, billed at $0.01 each plus the $0.10 source check.

🧾 JSON sample record

One real record from run h1kKeLkA8O37Abdfy, exactly as it lands in the dataset (emails masked, long text shortened):

{
"record_type": "press_release_record",
"schema_version": "1.0",
"run_id": "h1kKeLkA8O37Abdfy",
"publisher": "U.S. Securities and Exchange Commission",
"jurisdiction": null,
"source_feed_url": "https://www.sec.gov/news/pressreleases.rss",
"release_id": "29d9b3fa-0eed-432e-850c-0978c0f4c49b",
"composite_key": "sec.gov|29d9b3fa-0eed-432e-850c-0978c0f4c49b",
"title": "SEC Issues “Innovation Exemption” to Facilitate the Trading of Tokenized NMS Stock and Request for Comment",
"canonical_url": "https://www.sec.gov/newsroom/press-releases/2026-90-sec-issues-innovation-exemption-facilitate-trading-tokenized-nms-stock-request-comment",
"published_at": "Thu, 17 Sep 2026 08:55:00 -0400",
"updated_at": null,
"authors": [],
"categories": [],
"language": null,
"summary": "The Securities and Exchange Commission today issued an order granting temporary, conditional exemptive relief to Tokenized Securities Venues each a “TSV” from the definition of “exchange” in the Securities Exchange Act of 1934 (Exchange Act",
"body_text": null,
"body_truncated": false,
"attachments": [],
"source_url": "https://www.sec.gov/news/pressreleases.rss",
"observed_at": "2026-09-17T17:46:14Z",
"content_hash": "68fde85951448e5478bb85125afb8030b8868da34384c2e3bb7d91a789b7512f"
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy.

Watch semantics. Snapshot mode (watch_mode: false) returns a preview. Watch mode keys every record on a source-native id, stores a private baseline in a named key-value store, and on each later run emits one delta row per change (new / changed / removed). A blocked fetch is never diffed, so a source outage cannot show up as a mass removal.

Terminal states. A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

Charging. Each press-release delta is charged at the moment it is pushed (press-release-delta); a row that fails to charge is not delivered, so the dataset count always equals the charged count. One source-check is charged per run that actually read the source.

1. What it does

This actor watches buyer-supplied public RSS, Atom, JSON Feed, or approved official-newsroom listing adapters. It normalizes releases into one schema, stores a private key-value baseline, emits zero alerts on the first (seed) run, and emits record-backed deltas thereafter. Snapshot mode (watchMode:false) returns current release records. Use it for regulator, public-company, agency, and institution release monitoring where repeatable records matter. It does not use licensed press-wire sources.

5. Watch mode

The first watch run seeds a private baseline and emits zero deltas. Later scheduled runs emit only confirmed changes. A release is retracted_release only when detectRetractions is on, its article detail returns 404/410, and that repeats for retractionConfirmations consecutive eligible runs — disappearance from a rolling feed is never enough. Same release = lowercase registrable publisher domain plus release id; no fuzzy or cross-publisher matching. Partial or blocked checks never overwrite a healthy baseline.

8. Honest limits

No source discovery; no arbitrary selectors; no licensed press wires; no login/paywall/CAPTCHA bypass. Feed disappearance does not prove retraction. Publisher HTML and taxonomy changes can stop an adapter. Publication/update time may be null when the publisher omits it. Live coverage and counts depend on the configured sources. Blocked sources fail loud, never as a silent empty.

9. Compliance

Public logged-out sources only; no wall-defeating; no CAPTCHA/login/paywall workarounds; comply on objection. No login, private/licensed data, or always-on process. Buyers supply the newsroom feeds and are responsible for lawful use and source terms.

Preview vs Watch mode

  • Preview / snapshot (watchMode = false): returns current press releases for the feeds (billed per press-release-record). No baseline retained.
  • Watch (watchMode = true): seeds a private baseline on the first run (zero deltas), then emits only qualified press-release-delta rows against it. Each source reaching a usable/CAPPED read charges one source-check. source_receipt diagnostics go to the RUN_RECEIPT key-value record and log — never the dataset.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

⏰ Set it on a schedule

A single run is a snapshot. The value is the feed: open the actor in Apify Console → SchedulesCreate new, add this actor with input 3 above (watch_mode: true), and pick a cadence:

  • Daily0 7 * * * (07:00 UTC): catch changes within a day.
  • Weekly0 7 * * 1: a Monday digest.

Each run is independent; keep the same input on the schedule so the results stay comparable. Schedules can also POST results to a webhook (Console → Integrations).

💰 Pricing example

EventFreeBronzeSilverGold
Actor Start (apify-actor-start)$0.02$0.02$0.02$0.02
Press-release record (press-release-record)$0.005$0.0045$0.004$0.0034
Press-release delta (press-release-delta)$0.01$0.01$0.01$0.01
Source check (source-check)$0.10$0.09$0.08$0.07

Worked at the live Free-tier price (watch mode, one delta per change):

  • 8 press-release deltas: $0.02 start + $0.10 source check + 8 × $0.01 = $0.24
  • 25 press-release deltas: $0.02 start + $0.10 source check + 25 × $0.01 = $0.49
  • 1000 press-release deltas: $0.02 start + $0.10 source check + 1000 × $0.01 = $15.12

A run that delivers zero rows charges the $0.02 start fee plus the $0.10 source check (the source was read and reported empty). A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: NORMAL: records=25; sources_complete=1/1. maxItems is a hard ceiling on what is delivered and billed, never a target.

This actor reads public data only. It collects only what the source publishes to any visitor, identifies itself, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input (in watch mode the first run always seeds the baseline and returns zero deltas); BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee plus one source check.

Q: How many rows can one run return?
A: Up to maxItems (default 1000). Raise the cap for a bigger run; you pay per delivered row.

Q: What does watch mode remember between runs?
A: A private baseline of source-native record ids in a named key-value store. Each later run diffs the live source against it and emits only changes.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs except the watch baseline. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other market announcement watches actors?
A: Same output shape and billing model; this one covers 📰 Press-Release Event Feed — Official Newsroom Watch. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

🆘 Troubleshooting

  • Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
  • Status says CAPPED → your cap (maxItems) was reached → raise it for a bigger run.
  • Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
  • Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
  • First watch run shows no deltas → expected: it seeds the baseline; changes appear from the second run.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.