# Ausschreibungs-Monitor DACH – Public Tenders DE, AT, CH (`dach-data/german-tender-radar`) Actor

Public tenders from Germany, Austria and Switzerland from official open sources: EU TED, German Datenservice Öffentlicher Einkauf (incl. below threshold), Austrian Kerndaten, optionally simap.ch. Filter by keyword, CPV, region, deadline; only new tenders per run, digest and webhook alerts.

- **URL**: https://apify.com/dach-data/german-tender-radar.md
- **Developed by:** [dach-data](https://apify.com/dach-data) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$5.00 / 1,000 new tender delivereds

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

## Ausschreibungs-Monitor DACH – Public Tenders DE, AT, CH

**Public tenders from Germany, Austria and Switzerland, from official open sources, filtered to what you sell, delivered only once.**

German public procurement is split across portals. Above EU thresholds, tenders appear on **TED**. Below the thresholds (the large majority for small and mid-sized companies) they appear on the federal **Datenservice Öffentlicher Einkauf** (oeffentlichevergabe.de) and on **service.bund.de**. This Actor queries official, openly licensed sources (TED and the Datenservice Öffentlicher Einkauf; service.bund.de optionally, title and link only), merges duplicates and returns one clean list. It covers what these sources publish; tenders that appear only on other portals (for example some state or municipal platforms) are not included, so the feed is not guaranteed to be complete.

Optionally it also covers **Austria** (TED plus the legally required *Kerndaten* open-data sources under BVergG, incl. below-threshold tenders) and **Switzerland** (simap.ch). Choose with `countries`; default is Germany only. simap.ch is off by default: to get Swiss tenders, select Switzerland under `countries` and add `simap` under `sources`. Please check the simap.ch terms yourself before reusing Swiss data commercially.

### What you get

- **One feed, official sources:** Germany: EU TED Search API, Datenservice Öffentlicher Einkauf (daily OCDS export, incl. below-threshold tenders) and optionally the service.bund.de tender feed (title, deadline and link only). Austria: TED and the Kerndaten sources listed on data.gv.at. Switzerland: simap.ch (optional, off by default).
- **Country field:** every item has `country` (`DE`, `AT`, `CH`), so mixed feeds are easy to split.
- **Only new tenders:** with `onlyNew` the Actor remembers what it already delivered. Schedule it daily and you see each tender once, and you only pay for new ones.
- **Filters that matter for bidders:** keywords, exclusion words, CPV prefixes (e.g. `72` = IT services), Bundesland or canton (`Bayern`, `NRW`, `Steiermark`, NUTS codes like `DE21` or `AT13`, Swiss cantons like `CH-ZH`) and minimum days until the submission deadline.
- **Duplicates merged:** a tender published on TED and nationally appears once, with `alsoPublishedIn`.
- **Alerts:** optional webhook (Slack, Microsoft Teams workflow, Discord, Zapier, Make, n8n) receives a Markdown digest and all new tenders. The digest is also stored as `DIGEST` in the key-value store.
- **Robust:** if one portal is down, the others still deliver; the run only fails if no source is reachable, and the "already seen" memory is never overwritten by an empty run.

### Typical use

| Who | Setup |
|---|---|
| IT service provider in Bavaria | keywords `software, it-dienstleistung`, CPV `72`, regions `Bayern`, daily schedule, Slack webhook |
| Cleaning company in NRW | CPV `9091`, regions `NRW`, minDaysToDeadline `10` |
| Construction firm, several states | CPV `45`, regions `Sachsen, Thüringen, Sachsen-Anhalt` |
| Supplier active in all of DACH | countries `DE, AT, CH`, sources incl. `simap`, CPV `33` (medical equipment), daily schedule |
| Consultants / tender services | no filters, `maxItems` 5000, export to your CRM |

### Output (one item per tender)

```json
{
  "source": "ted",
  "country": "DE",
  "id": "ted:612345-2026",
  "title": "Deutschland – IT-Dienstleistungen – Rahmenvertrag Softwareentwicklung",
  "buyer": "Stadt München, Referat für Informationstechnik",
  "city": "München",
  "nutsCodes": ["DE212"],
  "cpvCodes": ["72000000", "72200000"],
  "procedureType": "open",
  "publicationDate": "2026-10-09",
  "deadline": "2026-11-20",
  "estimatedValue": 450000,
  "currency": "EUR",
  "description": "Entwicklung und Pflege von Fachverfahren.",
  "url": "https://ted.europa.eu/de/notice/-/detail/612345-2026",
  "alsoPublishedIn": [],
  "sourceNotice": "Quelle: TED – Tenders Electronic Daily, © Europäische Union, https://ted.europa.eu. Auszug, gekürzt.",
  "isNew": true,
  "firstSeenAt": "2026-10-11T12:00:00.000Z"
}
```

Fields that a source does not provide are `null` (for example service.bund.de has no CPV codes, some Austrian Kerndaten sources have no region).

When several countries are selected and `maxItems` is reached, the newest tenders are delivered first; the rest follow in the next run when `onlyNew` is on (as long as they are within `daysBack`).

### Pricing

Pay per result: you are charged per **new tender delivered**. Runs that find nothing new cost only the Actor start. Use `maxItems` to cap the cost of a run.

### Data sources and licence

- TED Search API v3 (Publications Office of the EU), free, no key. Notices may be reused commercially (TED legal notice). © European Union.
- Datenservice Öffentlicher Einkauf, Beschaffungsamt des BMI, open data under CC0.
- service.bund.de RSS feed of tenders (Bundesverwaltungsamt): off by default; when enabled only title, buyer, deadline and link are passed on, no description.
- Austria: Kerndaten sources under the Bundesvergabegesetz, listed on data.gv.at (eForms, CC BY 4.0). Some sources are occasionally unreachable; the others still deliver.
- Switzerland: simap.ch public API (official procurement platform of the Confederation, cantons and municipalities), off by default, used under the simap.ch API terms. Whether those terms allow commercial reuse is not clearly settled; check them before you use Swiss data commercially. **This is not an official publication. The data published on www.simap.ch are authoritative.** Swiss notices are passed on from 08:00 (Swiss time) on their publication day.

Every item carries a `sourceNotice` with the source and licence. If you republish the data, keep that notice (required for CC BY 4.0 and the simap.ch terms). Tender texts are excerpts and may be shortened; the linked original notice is authoritative. No warranty for completeness or correctness.

The Actor only reads official public notices. Data protection: e-mail addresses and phone/fax numbers contained in tender descriptions are removed before output; the Actor does not collect contact persons. Buyer names are those of public bodies.

***

### Deutsch in Kürze

Öffentliche Ausschreibungen aus TED, dem Datenservice Öffentlicher Einkauf (auch unterhalb der EU-Schwellenwerte) und optional service.bund.de (nur Titel, Frist, Link) in einer Liste, auf Wunsch auch Österreich (TED und Kerndaten-Quellen nach BVergG) und die Schweiz (simap.ch, standardmäßig aus; unter `sources` zuschalten). Erfasst wird, was diese Quellen veröffentlichen; Ausschreibungen, die nur auf anderen Portalen stehen, fehlen, Vollständigkeit wird nicht zugesichert. Filter nach Land, Stichwort, CPV, Bundesland oder Kanton und Mindestfrist. Mit „Nur neue“ und einem täglichen Zeitplan sehen Sie jede Ausschreibung genau einmal und zahlen nur für neue Treffer. Jeder Eintrag enthält eine Quellenangabe (`sourceNotice`); Schweizer Einträge: Dies ist keine amtliche Veröffentlichung, massgebend sind die auf www.simap.ch veröffentlichten Daten. E-Mail-Adressen und Telefonnummern werden aus den Texten entfernt. Optional per Webhook direkt in Slack, Teams oder per Zapier/Make in Ihr E-Mail-Postfach.

***

### Impressum / Legal notice (§ 5 DDG)

Patrick Schüdzig\
E-Mail: patrick.schuedzig@hotmail.de

# Actor input Schema

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

Germany, Austria and/or Switzerland. Default: Germany only.

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

Keep tenders whose title or description contains at least one of these words (case-insensitive). Example: software, reinigung, photovoltaik. Leave empty for all.

## `excludeKeywords` (type: `array`):

Drop tenders containing any of these words.

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

CPV prefixes, e.g. 72 (IT services), 45 (construction), 90910000 (cleaning). Matched by prefix.

## `regions` (type: `array`):

Bundesland or canton names, NUTS codes or Swiss canton codes, e.g. Bayern, NRW, DE21, Steiermark, AT13, CH-ZH. Empty = whole country.

## `minDaysToDeadline` (type: `integer`):

Skip tenders whose submission deadline is closer than this. Tenders without a known deadline are kept.

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

Remembers what was already delivered (per state key) and only returns new tenders. Ideal for daily schedules.

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

How many days of publications to scan.

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

Which official sources to query. Only sources of the selected countries are used. service.bund.de and simap.ch are off by default: service.bund.de has no open licence, and for simap.ch commercial reuse is not clearly permitted by its terms. For Swiss tenders select Switzerland under Countries and add simap.ch here.

## `keepWithoutCpv` (type: `boolean`):

service.bund.de entries carry no CPV codes. If enabled, they are kept when your keywords match.

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

Upper limit of tenders returned (and charged) per run.

## `webhookUrl` (type: `string`):

Optional. Receives a POST with a Markdown digest (field text) and all new tenders (field items).

## `stateKey` (type: `string`):

Use different keys for different searches so their 'only new' memories stay separate.

## Actor input object example

```json
{
  "countries": [
    "DE"
  ],
  "keywords": [
    "software"
  ],
  "onlyNew": true,
  "daysBack": 3,
  "sources": [
    "ted",
    "oeffentlichevergabe",
    "kerndaten-at"
  ],
  "keepWithoutCpv": true,
  "maxItems": 500,
  "stateKey": "default"
}
```

# Actor output Schema

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

No description

## `digest` (type: `string`):

No description

## `stats` (type: `string`):

No description

# 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 = {
    "keywords": [
        "software"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("dach-data/german-tender-radar").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 = { "keywords": ["software"] }

# Run the Actor and wait for it to finish
run = client.actor("dach-data/german-tender-radar").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 '{
  "keywords": [
    "software"
  ]
}' |
apify call dach-data/german-tender-radar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dach-data/german-tender-radar"
        }
    }
}
```

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/UanPDoiRhCQ5EMJec/builds/iI3bKmY2jo8c6tLs2/openapi.json