# EU Tender Matcher: TED Public Procurement Alerts by CPV (`lotebo-lab/ted-tender-matcher`) Actor

Get only the new EU public tenders from TED that match your CPV codes, countries, minimum value and keywords, with buyer, deadline and official link.

- **URL**: https://apify.com/lotebo-lab/ted-tender-matcher.md
- **Developed by:** [Tarcio Elyakin Agra Diniz](https://apify.com/lotebo-lab) (community)
- **Categories:** Business, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$100.00 / 1,000 tender matcheds

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

## EU Tenders Scraper: TED Public Procurement Notices

Every working day Tenders Electronic Daily publishes hundreds of public contract notices, and the handful that fit what your company sells are buried in the rest.

Give it the CPV codes you sell under, the buyer countries you serve and a minimum contract value. It searches TED and returns one row per matching notice with eight public fields: title, buyer, country, CPV codes, value, deadline, publication number and the link to the notice.

### Input

```json
{
  "cpvCodes": ["45000000"],
  "countries": ["DEU", "PRT"],
  "minValueEur": 200000,
  "keywords": ["school"],
  "maxResults": 50
}
```

| field | type | default | notes |
|---|---|---|---|
| `cpvCodes` | array of strings | `[]` | CPV codes; a parent code such as `45000000` matches its children |
| `countries` | array of strings | `[]` | buyer country as a **three letter** code: `DEU`, `PRT`, `FRA`. A two letter code such as `DE` matches nothing |
| `minValueEur` | integer | 0 | notices below this value are dropped |
| `keywords` | array of strings | `[]` | matched against the notice title, case insensitive |
| `publishedSince` | string | — | date, to limit how far back the search goes |
| `maxResults` | integer | 100 | 1 to 5000 |

All filters are optional, but an empty input returns whatever TED published, which is a lot. Start with one CPV code and one country you already follow.

### Example output

The rows below are copied from `logs/corrida-local-2026-09-20.log` in this repository, lines 20 to 42. That is an end-to-end run of `src/main.py` in which the POST to `https://api.ted.europa.eu/v3/notices/search` is answered from `tests/fixtures/ted_search_page1.json`, because the build sandbox has no route to TED. The search returned 5 notices and 2 survived the filters above. No run against the live TED API exists yet.

The two matching notices, one row each (lines 20 and 21):

```json
{"announcement_url": "https://ted.europa.eu/en/notice/-/detail/00512345-2026", "buyer_country": "DEU", "buyer_name": "Stadt Dortmund", "cpv_codes": ["45214210", "45000000"], "deadline": "2026-10-30T12:00:00+02:00", "notice_title": "Construction of a primary school in Dortmund", "publication_number": "00512345-2026", "total_value_eur": 2400000.0}
```

```json
{"announcement_url": "https://ted.europa.eu/en/notice/-/detail/00512590-2026", "buyer_country": "PRT", "buyer_name": "Municipio de Braga", "cpv_codes": ["45214100"], "deadline": "2026-11-05T15:00:00+00:00", "notice_title": "Construction of a school canteen in Braga", "publication_number": "00512590-2026", "total_value_eur": 1250000.0}
```

The run summary, which repeats the criteria that produced those rows (line 23):

```json
{
  "matchedNotices": 2,
  "storedNotices": 2,
  "chargedEvents": 0,
  "criteria": {
    "cpv_codes": ["45000000"],
    "countries": ["DEU", "PRT"],
    "min_value_eur": 200000,
    "keywords": ["school"]
  }
}
```

The same log records, at lines 43 to 45, that the source answer carried seven personal fields (`contact-email`, `winner-person`, `jury-member-name-lot` and others) and that none of them, by name or by value, reached the dataset.

### Limits

- `countries` only accepts the three letter code. `DE` instead of `DEU` returns zero rows with no error, which looks like an empty result rather than a mistake in the input.
- A notice with no value published cannot pass a `minValueEur` above zero.
- `keywords` match the title only, not the body of the notice, and there is no stemming: `school` does not match `schools`.
- Notices are deduplicated by publication number inside a run.
- The deadline comes from the notice as published, with its own timezone. Always open `announcement_url` before preparing a bid.
- TED data is reusable: the European Commission decision of 12/12/2011 states it "can be freely reused, for commercial or non-commercial purposes" (https://ted.europa.eu/en/legal-notice), and the search API needs no key (https://docs.ted.europa.eu/api/latest/index.html).
- Charging: one event only, `tender-matched`, at US$ 0.10 per matching notice stored, as declared in `.actor/actor.json`. A run that finds nothing matching is not charged. There is no start fee charged by this Actor.

### What this Actor does not do

- It does not return contact details of anyone: no name, no e-mail, no telephone, for buyer, winner or jury member.
- It does not download the tender documents, the annexes or the specification files.
- It does not translate the notice; the title comes as TED published it.
- It does not write, submit or track a bid, and it does not score your chance of winning.
- It does not cover national procurement portals that do not publish to TED.
- It does not tell you whether you are eligible to bid.

# Actor input Schema

## `cpvCodes` (type: `array`):

Common Procurement Vocabulary codes to look for. Matching is hierarchical: 45000000 also returns every code below it, such as 45213150. Leave empty to accept any category.

## `countries` (type: `array`):

Three letter country codes of the buyers you care about, for example FRA, DEU, ESP, PRT. Leave empty to accept every country.

## `minValueEur` (type: `integer`):

Skip notices whose total value is below this amount in euros. Notices published without a value are skipped whenever this is above zero. Use 0 to keep every notice.

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

Words to look for in the notice title. A notice is kept when any one of them appears, ignoring upper and lower case. Leave empty to skip this filter.

## `publishedSince` (type: `string`):

Optional date, in the form YYYY-MM-DD, to look only at notices published on or after it. Leave empty to search every published notice.

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

Largest number of matching notices to store in the dataset for one run. Lower it to keep a run cheap and fast.

## Actor input object example

```json
{
  "cpvCodes": [
    "45000000"
  ],
  "countries": [
    "FRA",
    "DEU"
  ],
  "minValueEur": 0,
  "keywords": [
    "school"
  ],
  "maxResults": 100
}
```

# Actor output Schema

## `tenders` (type: `string`):

One item per matching notice (rowType tender), with eight public fields: notice\_title, buyer\_name, buyer\_country, cpv\_codes, total\_value\_eur, deadline, publication\_number and announcement\_url. No personal data is collected. The last item of every run is the rowType summary row, whose message field says how many notices were read from TED, how many matched and how many were stored, so a run with no match still explains itself.

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

The same totals as the summary row of the dataset: noticesRead, matchedNotices, storedNotices, chargedEvents, chargeLimitReached, chargeFailures and the criteria used in the run.

# 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 = {
    "cpvCodes": [
        "45000000"
    ],
    "countries": [
        "FRA",
        "DEU"
    ],
    "keywords": [
        "school"
    ],
    "publishedSince": ""
};

// Run the Actor and wait for it to finish
const run = await client.actor("lotebo-lab/ted-tender-matcher").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 = {
    "cpvCodes": ["45000000"],
    "countries": [
        "FRA",
        "DEU",
    ],
    "keywords": ["school"],
    "publishedSince": "",
}

# Run the Actor and wait for it to finish
run = client.actor("lotebo-lab/ted-tender-matcher").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 '{
  "cpvCodes": [
    "45000000"
  ],
  "countries": [
    "FRA",
    "DEU"
  ],
  "keywords": [
    "school"
  ],
  "publishedSince": ""
}' |
apify call lotebo-lab/ted-tender-matcher --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,lotebo-lab/ted-tender-matcher"
        }
    }
}
```

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/GrJofwAHaM00G1vDN/builds/oHipQo6LoGIO5gnm5/openapi.json