GOV.UK Press Release Feed — official search API avatar

GOV.UK Press Release Feed — official search API

Pricing

from $33.50 / 1,000 press-release records

Go to Apify Store
GOV.UK Press Release Feed — official search API

GOV.UK Press Release Feed — official search API

Press releases from the official GOV.UK search API — title, department, date, link. Filter by keyword or organisation. No API key; pay per release.

Pricing

from $33.50 / 1,000 press-release records

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

📣 GOV.UK Press Release Feed — official search API

Pull the most recent press releases from the official GOV.UK search API (www.gov.uk/api/search.json), filtered by government organisation and/or keywords. Each result is returned as a clean record — title, publication timestamp, organisation, summary and a link to the release on GOV.UK — ready for a media-monitoring, policy or comms pipeline.

Output is one press_release row per result; billing is pay-per-event, the value event being one press-release record (a $0.02 start fee per run, then $0.05 per press-release record). Source: www.gov.uk.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

GOV.UK Press Release Feed — official search API sample output — a table of real press-release record rows (title, url, public_timestamp, organisations) from run M8lp7fppOiCFyj2XI on build 0.1.9

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

titleurlpublic_timestamporganisationsdescriptiondocument_type
Chancellor announces Bank of England appointmentshttps://www.gov.uk/government/news/chancellor-announces-bank-of-englan2026-09-16T14:19:00Z["HM Treasury"]His Majesty the King and the Chancellor have appointed three new non-epress_release
New members appointed to NISTA Expert Advisory Councilhttps://www.gov.uk/government/news/new-members-appointed-to-nista-expe2026-09-10T09:00:05Z["National Infrastructure and Service Transformation Authority", "HM TAppointees bring extensive experience in infrastructure delivery, finapress_release
Chancellor takes axe to delays holding back growthhttps://www.gov.uk/government/news/chancellor-takes-axe-to-delays-hold2026-09-07T13:31:00Z["HM Treasury"]Chancellor John Healey has set out his plan to drive growth in every ppress_release
First ever Entrepreneurship Advisor appointed to the Treasuryhttps://www.gov.uk/government/news/first-ever-entrepreneurship-advisor2026-09-07T11:42:27Z["HM Treasury"]Alex Depledge MBE appointed by the Chancellor as first ever Entreprenepress_release
UK leads way in disrupting shadowy Russian sanctions evasion networkhttps://www.gov.uk/government/news/uk-leads-way-in-disrupting-shadowy-2026-08-31T21:58:43Z["HM Treasury", "National Crime Agency"]Chancellor calls on allies to step up their pressure on Russia and setpress_release
£100 million competition to back British AI companies to fix public sehttps://www.gov.uk/government/news/100-million-competition-to-back-bri2026-08-31T09:25:15Z["HM Treasury", "Cabinet Office"]£100 million fund competition will help promising British AI start-upspress_release
Treasury to call time on uncertainty for pubs and hotelshttps://www.gov.uk/government/news/treasury-to-call-time-on-uncertaint2026-08-24T09:02:00Z["HM Treasury"]Pub and hotel valuations will be made fairer as the government takes apress_release
Budget to move “power and money out of Westminster, and into every poshttps://www.gov.uk/government/news/budget-to-move-power-and-money-out-2026-07-31T14:03:00Z["HM Treasury"]Today (Friday 31 July), the Chancellor has confirmed that the date ofpress_release

The run finished with the status message: NORMAL: 10 press releases delivered (source reports 1019 total matches) | release-record billable=10 | release-record charged=10

✅ What you get

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) — e.g. press_release
  • title (string/null) — e.g. Chancellor announces Bank of England appointments
  • url (string/null) — e.g. https://www.gov.uk/government/news/chancellor-announces-bank-of-england-appointm
  • public_timestamp (string/null) — e.g. 2026-09-16T14:19:00Z
  • organisations (array/null) — e.g. ["HM Treasury"]
  • description (string/null) — e.g. His Majesty the King and the Chancellor have appointed three new non-executive d
  • document_type (string/null) — e.g. press_release
  • source (string/null) — e.g. https://www.gov.uk/api/search.json
  • query — e.g. {"organisations": ["hm-treasury"], "keywords": null, "count": 10}

⚙️ Sample inputs

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

{
"organisations": [
"hm-treasury"
],
"count": 10
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 10 × $0.05 release-record = $0.52 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
"organisations": [
"hm-treasury"
],
"count": 10
}

A bounded run for checking the field shape before scheduling.

3. A full-size run

{
"organisations": [
"hm-treasury"
],
"count": 10
}

The same input run on a schedule; each run is billed only for what it delivers.

🧾 JSON sample record

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

{
"record_type": "press_release",
"title": "Chancellor announces Bank of England appointments",
"url": "https://www.gov.uk/government/news/chancellor-announces-bank-of-england-appointments--2",
"public_timestamp": "2026-09-16T14:19:00Z",
"organisations": [
"HM Treasury"
],
"description": "His Majesty the King and the Chancellor have appointed three new non-executive directors to the Bank of England’s Court of Directors.",
"document_type": "press_release",
"source": "https://www.gov.uk/api/search.json",
"query": {
"organisations": [
"hm-treasury"
],
"keywords": null,
"count": 10
}
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. Every request carries an identified contact User-Agent.

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 record is charged at the moment it is pushed (release-record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

Source

The official GOV.UK search API, queried anonymously (no key), with a contact User-Agent.

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 the input you want, 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 (release-record)$0.05$0.04$0.04$0.03

Worked at the live Free-tier price:

  • 8 press-release records: $0.02 start + 8 × $0.05 = $0.42
  • 25 press-release records: $0.02 start + 25 × $0.05 = $1.27
  • 100 press-release records: $0.02 start + 100 × $0.05 = $5.02

A run that delivers zero rows charges the $0.02 start fee only. 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: 10 press releases delivered (source reports 1019 total matches) | release-record billable=10 | release-record charged=10.

This actor reads public, logged-out pages and feeds published by www.gov.uk. It collects only what the source publishes to any visitor, identifies itself with a contact User-Agent, 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 source (www.gov.uk) is read logged-out; 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; 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 only.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. 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 www.gov.uk. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 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.
  • Fewer rows than expected → the source had fewer items in scope → widen the input.
  • 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.

⭐ 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.