UK Unified Tender Feed — Find a Tender + Contracts Finder, Deduplicated

One deduplicated feed of UK public procurement notices from two official government sources, in a single consistent schema. Built for pipelines, not dashboards: no seat, no login, no contract — pay per run.

What you get

Every notice as one flat row with the same field names regardless of which portal it came from, plus the same procurement merged when it appears on both:

source · seenInSources · ocid · noticeId · sourceUrl · stage · title · description · procurementCategory · cpvCode · cpvDescription · cpvDivision · buyerName · buyerRegion · buyerPostcode · valueAmount · valueCurrency · publishedDate · deadlineDate · contractStartDate · contractEndDate · supplierNames · awardValueAmount · isFramework

Coverage — stated plainly

Source	Covered
Find a Tender (Central Digital Platform)	✅
Contracts Finder	✅
Public Contracts Scotland	❌ not yet
Sell2Wales	❌ not yet
eTendersNI	❌ not yet

Two of the UK's five procurement portals. If you need all five today, this Actor is not yet the right tool and you should look elsewhere — several subscription products cover more. Scotland is next on the roadmap.

What this is, and is not

This data is free and public, published by the UK government under the Open Government Licence v3.0. You can call the official APIs yourself:

• Find a Tender API documentation
• Contracts Finder API documentation

If you only need one source, use the official API directly — it is free and it is excellent. This Actor is a convenience layer for the case where the official APIs stop being convenient:

• The two APIs use different date parameters that mean different things — updatedFrom (last-updated) vs publishedFrom (publication date)
• Different ocid schemes, different release-id conventions, different pagination
• Values sometimes on the tender, sometimes only per-lot
• No shared identifier, so the same procurement appears twice with no way to tell it is the same contract
• Contracts Finder signals rate limiting with HTTP 403 and an HTML body, not 429

This Actor absorbs all of that and hands you rows.

Deduplication

The same procurement is frequently advertised on more than one portal, with different wording — "Cardiff Council" vs "The City of Cardiff Council", "Provision of School Catering Services" vs "School Catering Services (Provision of)". There is no shared ID.

We match on normalised buyer + normalised title, keep the record from the more authoritative source, record every portal it appeared in under seenInSources, and backfill any field the winning row was missing.

You are not charged for duplicates that get removed. Set includeDuplicates: true if you would rather see every portal's copy separately.

No personal data

Organisation-level data only. Contact names, emails, telephone and fax numbers present in the source feeds are stripped before anything is written, and an automated guard fails the run if any personal data survives. That guard is covered by tests that run on every change.

If you need named procurement officers, this Actor will never give you them. That is a deliberate design decision, not a gap.

Pricing

Pay-per-event: a small charge when a run starts, plus a per-notice charge for each unique notice returned. No subscription, no seat, no minimum.

Typical uses

• Nightly sync of new notices into a CRM or lead-scoring model
• Filtering by CPV division and contract value to a specific market
• Building a historical dataset of awards and suppliers
• Monitoring named buyers without paying for a per-seat platform

Input

Field	Default	Notes
sources	both	Which portals to pull from
dateFrom / dateTo	last 7 days	Applied as last-updated on Find a Tender, publication date on Contracts Finder — the closest equivalent each API offers
stages	all	planning, tender, award, implementation (last is Contracts Finder only, filtered automatically)
cpvDivisions	all	Two-digit CPV codes, e.g. 45 construction, 85 health
minValue	none	Notices with no stated value are always kept — a missing figure is not evidence of a small contract
includeDuplicates	false	Keep every portal's copy separately
maxItems	1000	Hard cap, applied after deduplication

Limitations — read before buying

• Two of five UK portals. Scotland, Wales and Northern Ireland not yet included.
• No personal or contact data, ever.
• Coverage and accuracy are those of the source APIs; we normalise, we do not correct.
• Contracts Finder volume is declining structurally — since the Procurement Act 2023 commenced on 24 February 2025, new notices publish to Find a Tender.
• Not a bid-management platform, not an alerting tool. It returns rows.

What a row actually looks like

Three real rows, trimmed to the columns most people use:

publishedDate	title	buyerName	valueAmount	deadlineDate	cpvDescription
2026-07-29	Provision of Highways Maintenance Services	Lancashire County Council	4500000	2026-09-15	Highway maintenance work
2026-07-28	Grounds Maintenance Services 2027-2031	Preston City Council	500000	2026-08-29	Planting and maintenance of green areas
2026-07-30	Supply of Laboratory Consumables	NHS Lancashire Teaching Hospitals	250000	—	Laboratory reagents

Every row also carries ocid, noticeId, sourceUrl, stage, description, procurementCategory, cpvCode, cpvDivision, buyerRegion, buyerPostcode, valueCurrency, contractStartDate, contractEndDate, supplierNames, awardValueAmount and isFramework.

Export as JSON, CSV, Excel or feed it straight through the Apify API.

Questions people ask before running it

Is this data free elsewhere? Yes. It is published by the UK government under the Open Government Licence and the official APIs are linked above. If you only need one source and you are happy calling an API, do that. This Actor is for when that stops being convenient.

How fresh is it? As fresh as the source. Notices appear here as soon as they appear on the portal. Run it on a daily or weekly schedule to pick up new notices automatically.

How far back can I go? Set the date window as far back as you like. Bear in mind older windows return more rows, and you are charged per row, so use maxItems to cap it.

Does it include contact details for the buyer? No, deliberately. Contact names, emails and phone numbers are stripped before anything is written, and an automated guard stops the run if any survive. If you need named contacts, this is not the right tool and never will be.

What does a typical run cost? The default settings return 250 notices. Scale from there — you are charged per row returned, so a small window costs very little.

Can I filter to my sector? Yes. Use cpvDivisions with two-digit CPV codes — 45 construction, 85 health and social care, 72 IT services, 79 business services, 77 grounds and agriculture. Combine with minValue to drop contracts below your threshold.

Why are some notices missing a value? Buyers do not always publish one. Those rows are kept deliberately: a missing figure is not evidence of a small contract, and dropping them would lose real opportunities.

Can I get this as a proper API instead of an Actor run? Every Apify Actor is callable via the Apify API, so you can trigger a run and collect the dataset programmatically.

What if it breaks? Raise an issue on the Actor. It is built on official documented APIs rather than scraped HTML, so it breaks far less often than a typical Store listing — and there is a published maintenance runbook behind it.

Data licence and attribution

Contains public sector information licensed under the Open Government Licence v3.0. Source: Find a Tender and Contracts Finder, Cabinet Office / Crown Copyright. Attribution is required if you republish.

---

UK government contracts data · public sector tender alerts · procurement opportunities feed · Find a Tender API · Contracts Finder API · OCDS notices · public sector bid leads · UK tender data for CRM · government contract awards dataset