# UK Public Tenders (Find a Tender + Contracts Finder) (`delfielectronics/uk-public-tenders`) Actor All UK public tenders in one feed: Find a Tender and Contracts Finder notices with CPV, buyer, region, value, deadline and awarded suppliers. Daily alerts with onlyNew. - **URL**: https://apify.com/delfielectronics/uk-public-tenders.md - **Developed by:** [Artur Flamandzki](https://apify.com/delfielectronics) (community) - **Categories:** Business, Lead generation - **Security:** Limited permissions - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing Pay per event This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## UK Public Tenders (Find a Tender + Contracts Finder in one feed) Get **every UK public tender in one clean feed**: above-threshold and Procurement Act 2023 notices from **Find a Tender (FTS)** and lower-value notices from **Contracts Finder (CF)**. Pipeline notices, calls for tenders, **awards with suppliers and values**, contracts, updates and cancellations, all mapped to one record format. No API key, no login, no proxy: the actor reads the official OCDS APIs of both services. Every notice becomes one record: OCID, release id, stage, title, description, **buyer (name, id, town, postcode, region)**, **CPV codes**, procurement method, goods/works/services, **estimated value**, **tender deadline**, places of delivery (NUTS/ITL codes and region names), awarded suppliers with values, SME/VCSE suitability and the link to the official notice. ### What you can use it for - **Tender alerts**: run it daily with **Only notices not returned before** and get only new notices for your CPV codes, keywords, regions or value range. - **Sales and business development**: find public buyers that purchase what you sell, before the deadline. - **Competitor intelligence**: who wins which contracts, for how much, with which buyers (award notices). - **Market research**: public demand by CPV code, region and buyer. - **AI agents and CRMs**: structured, deduplicated notices via the Apify API or MCP. ### How it works 1. For each UK calendar day in the window (newest first) and each source, the actor reads the official OCDS release packages page by page: Find a Tender `ocdsReleasePackages` and Contracts Finder `OCDS/Search`. 2. Within a source, only the latest release of each procedure (OCID) in the run is kept, mapped to one record; contact names, e-mails, phones and street addresses are never returned. 3. Your filters are applied: stages, keywords in the title, CPV prefixes, regions, buyers, value range, deadline. 4. With **Only notices not returned before**, a release is returned once per combination of filters (memory kept 60 days); a later release of the same procedure (e.g. its award) comes again: a ready-made tender alert. ### Input | Field | What it does | |---|---| | Sources | FTS (Find a Tender), CF (Contracts Finder); both by default | | Stages | Calls for tenders, awards and contracts by default; also planning, updates, cancellations | | Published in the last N days | 1 = yesterday and today (UK time, best for a daily schedule); up to 31 | | Keywords | Words in the title, e.g. `cleaning`, `software` | | CPV codes | Prefixes, e.g. `45` (construction works), `72` (IT services), `85` (health and social work) | | Regions | NUTS/ITL code prefixes such as `UKI` (London) or names as Contracts Finder writes them (`South East`) | | Buyers | Part of the buyer's name or its exact id, e.g. `NHS`, `GB-PPON-PZGG-1891-TDCX` | | Minimum / maximum value | In GBP; notices without a value are dropped when set | | Deadline from | Only notices with a tender deadline on or after this date | | Include description / suppliers | Description text and awarded suppliers (both on by default) | | Only notices not returned before | Ideal for daily schedules | | Max notices | Stop after this many | ### Output example ```json { "source": "CF", "ocid": "ocds-b5fd17-43dad516-3d0f-4c42-b547-c17aec4868f8", "releaseId": "b9681ef2-d281-4e67-b93f-7fa2a69ab36a-920461", "stage": "award", "tags": ["award"], "publishedAt": "2026-11-03T20:29:46Z", "title": "Civic Centre Strip out", "description": "Call-off contract from a framework.", "buyer": {"name": "Ashford Borough Council", "id": "GB-LAE-ASF", "locality": "ASHFORD", "postalCode": "TN231HU", "region": null, "country": "England"}, "cpv": {"main": "45000000", "all": ["45000000"]}, "procurementMethod": "selective", "mainCategory": "works", "value": {"amount": 133713.49, "currency": "GBP"}, "deadline": "2026-08-25T10:00:00+01:00", "regions": ["South East", "United Kingdom"], "status": "complete", "awards": [{"status": "active", "date": "2026-10-29T00:00:00Z", "value": {"amount": 133713.49, "currency": "GBP"}, "suppliers": [{"name": "Example Demolition Ltd", "id": "GB-COH-00000000"}]}], "suitability": {"sme": true, "vcse": false}, "url": "https://www.contractsfinder.service.gov.uk/Notice/b9681ef2-d281-4e67-b93f-7fa2a69ab36a" } ``` Stages: `planning`, `tender`, `award`, `contract`, `update`, `cancellation`. A release with several tags takes the latest one (Find a Tender award notices are tagged award + contract and count as `contract`). Values are net (`amount`) when published, else gross; `value` is the tender estimate (or the sum of its lots), award values are in `awards`. ### Pricing Pay per event, no subscription. The prices are on the **Pricing** tab; you are charged for two events: | Event | When | |---|---| | Source-day (`source-day`) | once per source and day read successfully (FTS and CF for 2 days = 4); a source that is down is not charged | | Notice (`notice`) | once per notice saved to the dataset | - A working day of both sources brings roughly 650 releases (measured on 3 November 2026: about 490 on Find a Tender and 165 on Contracts Finder); filters cut the notice fees, the source-day fee stays. - A source-day is charged only when your remaining budget also covers at least one notice. - The form starts with **Max notices** = 100 for a cheap first run; raise it for a full feed. - Set a maximum cost per run in Apify and the actor stops cleanly when it is reached. ### Data and privacy Contains public sector information licensed under the Open Government Licence v3.0 (https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/), published by the Cabinet Office on find-tender.service.gov.uk and contractsfinder.service.gov.uk. Buyers are public bodies. Suppliers are mostly companies, but sole traders may appear under their own name as published by law: the actor returns only a supplier's name and identifier, never contact data or street addresses, and **Include suppliers** off removes them. Use such records in line with the UK GDPR. ### Known limits - Find a Tender is read by update time, Contracts Finder by publication time: an FTS record's `publishedAt` is its release date and may fall outside the day it was read on. - The same procedure published on both services (they are not linked by OCID) is returned twice, with different `source`. - Regions: Find a Tender gives NUTS/ITL codes, Contracts Finder gives region names only. - With onlyNew off, releases are not remembered: turning onlyNew on later starts from an empty memory. - Notices are as published; corrections arrive as separate `update` releases. # Actor input Schema ## `sources` (type: `array`): FTS = Find a Tender (above-threshold and Procurement Act 2023 notices, whole UK); CF = Contracts Finder (lower-value notices, England). Both together cover UK central and local government tenders. ## `stages` (type: `array`): planning = pipeline and prior information; tender = open calls for tenders; award = awarded suppliers; contract = signed contracts (FTS award notices usually carry award and contract, and count as contract); update = corrections; cancellation = cancelled procedures. ## `publishedWithinDays` (type: `integer`): 1 = yesterday and today (UK time). Run daily with onlyNew for a tender alert feed. ## `keywords` (type: `array`): Keep notices whose title contains any of these words (case ignored, e.g. cleaning, software). Empty = all. ## `cpvCodes` (type: `array`): Keep notices with any CPV code starting with these digits (e.g. 45 = construction works, 72 = IT services, 85 = health and social work). Empty = all. ## `regions` (type: `array`): Keep notices whose buyer or place of delivery is in these regions: a NUTS/ITL code prefix (e.g. UKI = London, UKM = Scotland) or a region name as Contracts Finder writes it (e.g. London, South East). Empty = all. ## `buyers` (type: `array`): Keep notices whose buyer name contains any of these texts, or whose buyer id equals one of them (e.g. NHS, Leeds City Council, GB-PPON-PZGG-1891-TDCX). Empty = all. ## `minValue` (type: `integer`): Keep notices with an estimated value of at least this many pounds (net when published). Notices without a value in GBP are dropped when this is set. ## `maxValue` (type: `integer`): Keep notices with an estimated value of at most this many pounds. Notices without a value in GBP are dropped when this is set. ## `deadlineFrom` (type: `string`): Keep only notices whose tender deadline is on or after this date (YYYY-MM-DD); notices without a deadline are dropped when this is set. ## `includeDescription` (type: `boolean`): Add the notice description text. ## `includeSuppliers` (type: `boolean`): Add awarded suppliers (name and identifier as published, e.g. Companies House number) to award notices. ## `onlyNew` (type: `boolean`): Return only notice releases this actor has not returned to you before with the same filters (memory kept 60 days). A new release of the same procedure (e.g. its award) is returned again. ## `maxNotices` (type: `integer`): Stop after saving this many notices. The form starts at 100 for a cheap first run; the API default is 5000. ## Actor input object example ```json { "sources": [ "FTS", "CF" ], "stages": [ "tender", "award", "contract" ], "publishedWithinDays": 1, "keywords": [], "cpvCodes": [], "regions": [], "buyers": [], "includeDescription": true, "includeSuppliers": true, "onlyNew": false, "maxNotices": 100 } ``` # Actor output Schema ## `overview` (type: `string`): The run's notices in the Store table view. ## `results` (type: `string`): Every field of every notice record. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "maxNotices": 100 }; // Run the Actor and wait for it to finish const run = await client.actor("delfielectronics/uk-public-tenders").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "maxNotices": 100 } # Run the Actor and wait for it to finish run = client.actor("delfielectronics/uk-public-tenders").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "maxNotices": 100 }' | apify call delfielectronics/uk-public-tenders --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,delfielectronics/uk-public-tenders" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/DGCfWXSuWaNd8PJal/builds/vf8PMl90IQErRWUct/openapi.json