# UK Find a Tender — Notices, Values & Deadlines (`kaz_kakyo/uk-tender-notices`) Actor

Export official UK Find a Tender notices with buyer, CPV codes, source value and deadline. Filter a capped feed of updated notices or look up exact notice IDs. Partial scans are explicit; contacts excluded. $5 per 1,000 notices plus start.

- **URL**: https://apify.com/kaz\_kakyo/uk-tender-notices.md
- **Developed by:** [Heim AI](https://apify.com/kaz_kakyo) (community)
- **Categories:** Business, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 notice returneds

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 Find a Tender — Notices, Values & Deadlines

Export official **Find a Tender notice records** as structured JSON or CSV. Get notice and procurement identifiers, title, buyer organisation, CPV codes, the source's tender value, deadline and original notice link. Use a recent updated-date window or provide exact notice IDs.

This covers **Find a Tender**, not every UK procurement portal. A notice is not necessarily an opportunity open for bidding: planning notices, direct-award information, amendments and awards serve different purposes. Verify the original notice before acting.

### Quick start

```json
{"stage":"tender","daysBack":3,"maxResults":5,"maxScanned":100}
```

For an exact lookup:

```json
{"noticeIds":["089792-2026"],"maxResults":1}
```

The example ID is a real published notice, not a promise that bidding is currently open. Exact-ID mode takes precedence over date-window mode; title and CPV filters still apply.

### Filters and completeness

- `stage`: `tender` (default), `planning`, `award` or `all` for date-window queries.
- `daysBack`: 1–7 calendar dates through today, default3. Alternatively supply `updatedFromDate` and `updatedToDate` as `YYYY-MM-DD`, at most seven dates inclusive.
- `titleContains`: case-insensitive substring in the notice title.
- `cpvPrefix`: 2–8 digits matched against source CPV codes.
- `maxResults`: 1–200 paid notices, default25.
- `maxScanned`: 1–100 source notices examined, default100. Caps filtering cost and may end a search before all matching notices are found.

**The date filter is the source API's updated-date window, not publication date.** Requests cover the supplied date boundaries from 00:00:00 through 23:59:59 in the source API's date format. Returned source timestamps keep their supplied timezone offsets; the actor does not claim exact UTC window-edge semantics that the publisher documentation does not establish.

Title/CPV filtering examines only the first `maxScanned` unique notices encountered in the publisher’s pagination order. It is a capped feed filter, not an exhaustive search of the requested window.

Always check the free Status dataset and `OUTPUT.complete`. An empty result with `complete:false` is **not proof of no matching notices**. Results can be partial because of the scan, output, request, time or spending limit, or a source error.

### Price

**$0.005 per returned notice ($5/1,000), plus the configured $0.00005 platform start event.** Five returned notices cost $0.02505. Missing/failed notices and status rows have no work-event charge. A zero-match request incurs no notice charge. Set `maxResults` and the Console maximum-charge limit before running.

Each distinct `(ocid, noticeId)` is one record. Amendments with separate notice IDs are separate records; this is a notice feed, not a consolidated latest-state view of each procurement. The same notice returned by a new run is charged again. Use `recordId` to deduplicate overlapping exports yourself.

### Output details

Only notice records enter the default paid dataset. `tenderValueAmount` and currency come from `tender.value`; they are not inferred award spend. Values may be estimates or framework ceilings, and the actor does not infer whether VAT is included. Missing values and deadlines remain null. `submissionDeadline` alone does not prove bid eligibility. Contacts, suppliers, descriptions, attachments and personal profiles are excluded.

Run `kaz_kakyo/uk-tender-notices` through Apify's API, CLI, MCP or automation integrations. Scheduling repeats a snapshot search; no cross-run alerts or exactly-once delivery are promised.

Source: [UK Open Contracting documentation](https://www.gov.uk/government/publications/open-contracting). Every record carries its original notice URL and licence attribution. Contains public sector information licensed under the [Open Government Licence v3.0](https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/). No government endorsement is implied.

Pseudonymous operational telemetry records actor and run IDs, run origin, timestamps, paying-plan status, a stable hashed caller identifier, and cumulative confirmed event counts. These identifiers are linkable, not anonymous. The telemetry dataset restricts unauthenticated access. Input and result content is not sent. If paid delivery is interrupted, resurrect the **same run** to recover pending records without another charge.

New source work has an internal three-minute budget with time reserved to save output; a larger platform timeout does not extend it. Keep run storage intact when resurrecting. Invalid saved limits stop new work after pending paid records have been recovered.

# Actor input Schema

## `noticeIds` (type: `array`):

Up to 10 IDs such as 089792-2026. When supplied, fetch these notices instead of a date-window list. Filters still apply.

## `stage` (type: `string`):

Source stage for date-window queries. Award and planning notices are not necessarily opportunities to bid.

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

1–7 calendar dates through today, unless explicit updated dates are supplied. This filters source updates, not publication.

## `updatedFromDate` (type: `string`):

YYYY-MM-DD; source API date boundary, not a guaranteed UTC publication window.

## `updatedToDate` (type: `string`):

YYYY-MM-DD; defaults to today. Maximum seven calendar dates inclusive.

## `titleContains` (type: `string`):

Case-insensitive substring matched after fetching. A capped scan is partial, even with no matches.

## `cpvPrefix` (type: `string`):

2–8 digits matched against source CPV classifications. No semantic or fuzzy matching.

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

Hard cap on paid notice records. Amendments with different notice IDs are separate records.

## `maxScanned` (type: `integer`):

Limits filtering work to at most100 notices. Check the free status summary for completeness.

## Actor input object example

```json
{
  "noticeIds": [],
  "stage": "tender",
  "daysBack": 3,
  "titleContains": "",
  "cpvPrefix": "",
  "maxResults": 5,
  "maxScanned": 100
}
```

# Actor output Schema

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

Only successfully returned records, with all fields.

## `status` (type: `string`):

Check complete and stop reasons even when the run succeeds or results are empty.

# 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 = {
    "maxResults": 5
};

// Run the Actor and wait for it to finish
const run = await client.actor("kaz_kakyo/uk-tender-notices").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 = { "maxResults": 5 }

# Run the Actor and wait for it to finish
run = client.actor("kaz_kakyo/uk-tender-notices").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 '{
  "maxResults": 5
}' |
apify call kaz_kakyo/uk-tender-notices --silent --output-dataset

```

## MCP server setup

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

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/DXupCUQnGaXLQuZ1k/builds/ZQftbvqbwQLNL2X25/openapi.json