# DACH Tenders & Procurement Monitor (`highbrow_qualification_z7w/eu-tenders-monitor`) Actor

Search and monitor public procurement notices in Germany, Austria, and Switzerland via the official TED API. Filter by keywords, country, CPV code, publication date, and deadline. Export structured results or track only newly published notices.

- **URL**: https://apify.com/highbrow\_qualification\_z7w/eu-tenders-monitor.md
- **Developed by:** [Roman Bublyk](https://apify.com/highbrow_qualification_z7w) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.10 / 1,000 results

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

## DACH Tenders & Procurement Monitor

Search and monitor public procurement notices in Germany, Austria, and Switzerland through the official [TED Search API](https://docs.ted.europa.eu/api/latest/search.html). Filter notices by keywords, place of performance, CPV code, publication date, or submission deadline, then export structured results from the Apify Dataset.

### What this Actor does

- Searches published TED notices without browser scraping or authentication.
- Limits searches to Germany (`DE`), Austria (`AT`), and Switzerland (`CH`) by place of performance.
- Filters by keyword, Common Procurement Vocabulary (CPV) code, publication date, and submission deadline.
- Returns ready-to-use Dataset records with buyer, value, dates, and a direct TED link.
- Supports scheduled monitoring with `onlyNew` to emit newly seen notices only.
- Enforces a `maxItems` limit of 1–1,000 to control result volume and cost.

### Common use cases

- Monitor new public tenders for a sales or business-development team.
- Find DACH opportunities matching a service, product, or CPV category.
- Build a procurement feed for a CRM, spreadsheet, dashboard, or notification workflow.
- Run a scheduled search and receive only notices not returned by previous runs.

### Input

| Field | Type | Default | Description |
| --- | --- | --- | --- |
| `keywords` | string | `""` | Words or a phrase to search for in procurement notices. |
| `countries` | array | `["DE"]` | Countries of contract performance: `DE`, `AT`, or `CH`. |
| `cpvCodes` | array | `[]` | Optional CPV codes. Values may contain 2–8 digits and may end in `*` for a prefix search. |
| `publishedFrom` | string | — | Earliest publication date, in `YYYY-MM-DD` format. |
| `submissionDeadlineFrom` | string | — | Earliest submission deadline, in `YYYY-MM-DD` format. |
| `maxItems` | integer | `50` | Maximum number of notices to retrieve, from `1` to `1,000`. |
| `onlyNew` | boolean | `false` | Return only notices not seen by a previous monitoring run. |

#### Example input

```json
{
  "keywords": "software development",
  "countries": ["DE", "AT"],
  "cpvCodes": ["72000000"],
  "publishedFrom": "2026-09-01",
  "submissionDeadlineFrom": "2026-10-01",
  "maxItems": 100,
  "onlyNew": false
}
```

Dates must use `YYYY-MM-DD`. For example, use `2026-09-01`, not `01.09.2026`.

### Output

Every Dataset record includes the following fields when TED publishes them:

```json
{
  "noticeId": "639938-2026",
  "title": "Example procurement notice",
  "buyer": "Example contracting authority",
  "country": "DEU",
  "placeOfPerformance": "DE126",
  "cpvCodes": ["45000000"],
  "estimatedValue": 200000,
  "currency": "EUR",
  "publishedAt": "2026-09-17",
  "submissionDeadline": "2026-10-20",
  "url": "https://ted.europa.eu/en/notice/-/detail/639938-2026",
  "collectedAt": "2026-09-17T18:04:06.000Z"
}
```

`estimatedValue`, `currency`, and `submissionDeadline` may be absent when they are not published in the underlying TED notice.

### Monitor only new notices

Set `onlyNew` to `true` and schedule the Actor in Apify.

- The first matching run returns the currently available notices and saves their IDs.
- Later matching runs return only notice IDs not previously stored by this Actor.
- The Actor retains up to 10,000 recently seen IDs in a named key-value store.
- The stored-ID history is shared across all runs of this Actor. Use a separate Actor or reset its state when you need independent monitoring histories for different filters.

For most tender searches, a daily or weekly schedule is appropriate. Start with a small `maxItems` value and increase it only when needed.

### Limitations

- Results reflect data returned by the TED Search API at the time of the run.
- The Actor searches published notices; it does not download tender documents or submit bids.
- It currently supports only Germany, Austria, and Switzerland as places of performance.
- Search language, completeness of values, and deadlines depend on the notice data published in TED.

### Local development

```bash
npm install
npm test
npm start
```

Node.js 20 or newer is required.

### Data source and disclaimer

- [TED API documentation](https://docs.ted.europa.eu/api/latest/index.html)
- [TED Search API](https://docs.ted.europa.eu/api/latest/search.html)

TED public data is accessed directly through the official API. This project is not affiliated with or endorsed by the Publications Office of the European Union.

# Actor input Schema

## `keywords` (type: `string`):

Words or phrases to search for in procurement notices.

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

Countries in which the contract will be performed.

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

Optional Common Procurement Vocabulary codes.

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

Optional earliest publication date in YYYY-MM-DD format.

## `submissionDeadlineFrom` (type: `string`):

Optional earliest submission deadline in YYYY-MM-DD format.

## `maxItems` (type: `integer`):

Hard cost guard. The run stops after this many notices.

## `onlyNew` (type: `boolean`):

After the first run, output only notice IDs not seen before.

## Actor input object example

```json
{
  "keywords": "",
  "countries": [
    "DE"
  ],
  "cpvCodes": [],
  "maxItems": 50,
  "onlyNew": false
}
```

# Actor output Schema

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

Structured procurement notices returned by the TED Search API.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("highbrow_qualification_z7w/eu-tenders-monitor").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("highbrow_qualification_z7w/eu-tenders-monitor").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 '{}' |
apify call highbrow_qualification_z7w/eu-tenders-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,highbrow_qualification_z7w/eu-tenders-monitor"
        }
    }
}
```

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/BrSqbGwi5NJdHUNYy/builds/tyEUKyex3dEmaNGdT/openapi.json