# UK Tender Finder: Contracts Finder & Find a Tender (`kirozhang/uk-tender-opportunity-finder`) Actor

Find UK procurement notices from two official OCDS feeds. Filter keywords, CPV, value and SME suitability; export buyers, deadlines and source links.

- **URL**: https://apify.com/kirozhang/uk-tender-opportunity-finder.md
- **Developed by:** [Kiro Zhang](https://apify.com/kirozhang) (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

$5.00 / 1,000 matching procurement notices

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 Tender Finder: Contracts Finder & Find a Tender

Build a repeatable shortlist of UK public-sector procurement notices using Contracts Finder and Find a Tender. Filter official records into a dataset your bid team can review or send to a spreadsheet.

### Who this is for

For bid teams and suppliers building a repeatable UK procurement shortlist. Search Contracts Finder and Find a Tender in one run, then review the original notices before deciding to bid.

Start with at most 10 result rows: the Actor event charges for that batch are at most $0.05 at the listed rate. Set both `maxResults` and the run's maximum charge before starting.

### Quick start

Open the Input tab, paste your input and run. A small example:

```json
{
  "daysBack": 2,
  "maxNotices": 10,
  "maxPagesPerSource": 2,
  "onlyOpen": true,
  "stages": [
    "tender"
  ],
  "maxResults": 10
}
```

### Two official feeds, one output

Rows include notice ID, OCID, buyer, title, description, stage, status, value and currency, CPV codes, deadlines, SME suitability when supplied, source documents and a notice link. Missing values stay `null`; no budget, deadline or SME status is invented. Public-sector information is attributed under the [Open Government Licence v3.0](https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/).

### Build a useful daily shortlist

Use `keywords` such as `["cyber security", "software"]` or CPV prefixes such as `["72"]`. Keywords use OR matching. Set `onlySmeSuitable` only if you want to exclude notices without explicit suitability data. `minValueGbp` filters on stated GBP tender values; it does not convert currencies or substitute award values.

For a first exploratory run, leave keywords empty. A narrow query can legitimately return no matching rows. When repeating searches, use `(source, noticeId)` to deduplicate in your downstream workflow; overlapping dates and repeated runs can return the same notice.

### Coverage is bounded and visible

The date window selects publication time on Contracts Finder and update time on Find a Tender. It is a notice-window search, not an inventory of all currently open contracts. Each source is paged in turn; matching rows from fetched pages are sorted by notice date. Small page/result caps can omit matches, including newer notices on unread pages. Always inspect `RUN_SUMMARY.sources` for scanned counts, page counts, errors and completeness before drawing conclusions.

Separate source notices are not heuristically merged. Planning and award stages are coarse classifications from OCDS release tags. Deadlines labelled `enquiry_only` are not bid deadlines. Confirm the current conditions on the official notice before acting.

Source documentation: [Contracts Finder OCDS](https://www.contractsfinder.service.gov.uk/apidocumentation/Notices/1/GET-Published-Notice-OCDS-Search), [Find a Tender OCDS](https://www.find-tender.service.gov.uk/apidocumentation/1.0/GET-ocdsReleasePackages).

### Pricing and limits

$5 per 1,000 delivered matching procurement notice results ($0.005 each). There is no Actor startup fee. Standard platform usage is included in this Actor's event price. A successfully delivered dataset row triggers one charge; error diagnostics live in `RUN_SUMMARY` and are not chargeable rows. Repeated runs are new checks and may return the same item again. The Pricing tab is authoritative.

Use the run's maximum charge setting and `maxResults` to control spending. No proxy subscription or external API key is required. Runs use 256 MB by default. For large batches, raise the run timeout or split the input; a hard timeout may leave an incomplete dataset. The presence of a finished `RUN_SUMMARY` helps distinguish completed processing from interrupted runs.

### Export and integrations

Use the Output tab to inspect results and the summary. Download JSON, CSV or Excel from the dataset, or use Apify's API, Make, Zapier or n8n to pass the output into your existing workflow. Nested evidence is most faithfully preserved in JSON. The default dataset belongs to the run; no external destination receives results automatically.

An API client can start `kirozhang/uk-tender-opportunity-finder` with the JSON above, wait for completion and read its default dataset. Set your Apify token in the client's credential store, never inside the input URLs.

### Troubleshooting

Read `RUN_SUMMARY.errors` and `limitReasons` first. A partial run may contain useful rows; it must not be treated as exhaustive. All-target failure marks the run failed. A valid search with no matches can succeed with zero rows. For support, open an Issue on this Actor with the run ID, expected behavior and a public example target. Remove credentials and private data from your report.

### Example output

Illustrative excerpt from a real verification run; values change over time.

```json
{
  "title": "Marple Memorial Park Active Environments Project",
  "buyerName": "Stockport Metropolitan Borough Council",
  "stage": "award",
  "deadline": "2025-10-31T12:00:00Z",
  "valueAmount": 118108.58,
  "currency": "GBP",
  "source": "contractsFinder",
  "url": "https://www.contractsfinder.service.gov.uk/Published/Notices/OCDS/Search?limit=100&publishedFrom=2026-11-04T12%3A35%3A43.807Z&publishedTo=2026-11-06T12%3A35%3A43.807Z"
}
```

### Workflows and questions

#### A daily shortlist for a bid team

1. Run the broad two-day example first to inspect the available fields. Then add the team's keywords or CPV prefixes.
2. Save the input as an Apify task and choose a daily schedule in your timezone. A two-day lookback intentionally overlaps successive runs.
3. In your spreadsheet or database, upsert on `(source, noticeId)` to avoid sending the same notice to your team repeatedly.
4. Retain the source URL and collection time. Inspect `RUN_SUMMARY.sources`: unread pages or result limits mean the shortlist is partial.

#### Common questions

**Does it list every currently open UK contract?** No. It searches notices in a bounded publication/update window and respects source/page/result caps.

**Why did a narrow search return zero?** No matching notice may have been found in the pages scanned. Remove one filter at a time and inspect coverage before extending the date window.

**Are missing values estimated?** No. Unknown budgets, deadlines and SME suitability stay explicit. Enabling the SME or value filter can exclude notices with missing data.

### API quick start

Save the Quick start JSON as `input.json`. Put your Apify token in the `APIFY_TOKEN` environment variable through your usual secret store, then run:

```bash
curl --fail-with-body --max-time 200 \
  --request POST \
  --header "Authorization: Bearer $APIFY_TOKEN" \
  --header "Content-Type: application/json" \
  --data-binary @input.json \
  "https://api.apify.com/v2/acts/kirozhang~uk-tender-opportunity-finder/run-sync-get-dataset-items?timeout=180&memory=256&maxTotalChargeUsd=0.10&format=json&clean=true" \
  --output results.json
```

This example starts a real run and applies a $0.10 charge ceiling. The smaller `maxResults` cap still applies. An empty array can be a valid no-match result; inspect the run and `RUN_SUMMARY` in Console. If the connection times out, check Console before retrying, since the run may already exist. For larger exports, use the asynchronous API shown on this Actor's API tab and read the dataset after the run finishes.

### Scheduling and workflow tools

After a successful small run, save a task with your production input. [Apify schedules](https://docs.apify.com/actors/running/schedules) can run that task regularly. In Make, Zapier or n8n, store the token in the connection credentials, run this Actor, wait for completion, and read its dataset. Configure your own destination explicitly; this Actor does not send emails or post messages automatically. Each scheduled run may incur charges, including repeated results.

### Related tools for different steps

- [For a published buyer or supplier website you already know, collect public technology evidence for account research.](https://apify.com/kirozhang/website-tech-stack-evidence)

# Actor input Schema

## `sources` (type: `array`):

Choose contractsFinder and/or findATender. Both are used by default.

## `daysBack` (type: `integer`):

Used when explicit date bounds are absent. The maximum search window is 31 days.

## `publishedFrom` (type: `string`):

ISO 8601 date or UTC timestamp. Contracts Finder uses publication time; Find a Tender uses update time.

## `publishedTo` (type: `string`):

ISO 8601 date or UTC timestamp, no later than now. Defaults to the current time.

## `keywords` (type: `array`):

Case-insensitive OR matching in title and description. Empty means no keyword filter.

## `cpvPrefixes` (type: `array`):

Match the start of any CPV code, for example 72 for IT services.

## `stages` (type: `array`):

Choose tender, planning and/or award. Default: tender. Use an empty array for all stages.

## `onlyOpen` (type: `boolean`):

Exclude non-active tenders and tenders with expired tender deadlines. Unknown deadlines remain null; planning and award notices are unaffected.

## `onlySmeSuitable` (type: `boolean`):

Exclude notices where SME suitability is false or unknown.

## `minValueGbp` (type: `integer`):

Zero disables this filter. Unknown amounts and non-GBP values are excluded when enabled.

## `maxNotices` (type: `integer`):

Global result cap across both sources. Also limited by maxResults and your charge budget.

## `maxPagesPerSource` (type: `integer`):

Each source page contains at most 100 releases. Increase for coverage; the summary identifies partial searches.

## `maxResults` (type: `integer`):

Additional global cap for this run. Stops before another paid result is saved. The lower of this value, product-specific caps and your charge budget applies.

## Actor input object example

```json
{
  "sources": [
    "contractsFinder",
    "findATender"
  ],
  "daysBack": 2,
  "keywords": [],
  "cpvPrefixes": [],
  "stages": [
    "tender"
  ],
  "onlyOpen": true,
  "onlySmeSuitable": false,
  "minValueGbp": 0,
  "maxNotices": 100,
  "maxPagesPerSource": 3,
  "maxResults": 500
}
```

# Actor output Schema

## `results` (type: `string`):

Delivered rows, exportable as JSON, CSV or Excel.

## `summary` (type: `string`):

Counts, limits and unbilled errors. Check complete before treating the result as exhaustive.

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "sources": [
        "contractsFinder",
        "findATender"
    ],
    "keywords": [],
    "cpvPrefixes": [],
    "stages": [
        "tender"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("kirozhang/uk-tender-opportunity-finder").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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "sources": [
        "contractsFinder",
        "findATender",
    ],
    "keywords": [],
    "cpvPrefixes": [],
    "stages": ["tender"],
}

# Run the Actor and wait for it to finish
run = client.actor("kirozhang/uk-tender-opportunity-finder").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 '{
  "sources": [
    "contractsFinder",
    "findATender"
  ],
  "keywords": [],
  "cpvPrefixes": [],
  "stages": [
    "tender"
  ]
}' |
apify call kirozhang/uk-tender-opportunity-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,kirozhang/uk-tender-opportunity-finder"
        }
    }
}
```

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 <APIFY_API_TOKEN>` 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/HfztN0a9FhaZqnyL6/builds/uJhotfsLNLTIv08da/openapi.json