# German Procurement Monitor (oeffentlichevergabe.de, by CPV) (`chosen_loafer/german-procurement`) Actor

Monitors new German public tenders from oeffentlichevergabe.de (Bekanntmachungsservice), Germany's national e-procurement notice portal, filtered by CPV code with deadline tracking. No personal data is collected.

- **URL**: https://apify.com/chosen_loafer/german-procurement.md
- **Developed by:** [Pavel Staurouski](https://apify.com/chosen_loafer) (community)
- **Categories:** Lead generation, Automation, Business
- **Stats:** 2 total users, 1 monthly users, 94.1% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 tender checkeds

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

## German Procurement Monitor (oeffentlichevergabe.de, by CPV)

Monitors new German public tenders published on oeffentlichevergabe.de (the
Bekanntmachungsservice, Germany's national e-procurement notice portal), filtered by CPV
code and publication date.

### What you get

One record per matching tender lot: notice identifier, lot identifier, title, CPV code,
submission deadline, publication date, the contracting authority's name, the notice type,
and a link to the official notice page. Nothing about named individuals. A multi-lot
tender produces one record per lot, since different lots of the same procedure can cover
different CPV divisions and close on different dates.

### What it does not do

No contact-person data of any kind, no attached tender documents, no full notice text
beyond the structured fields needed for CPV filtering and deadline tracking. This Actor
only ever calls the public search/list endpoint; it deliberately never calls the
per-notice detail endpoint, which is the only place a contact person's name, email, phone
or fax number could appear.

### Why you might need this

Below-EU-threshold German tenders (the majority by count) never reach TED. German public
bodies (federal, state and most municipal) publish them on oeffentlichevergabe.de instead,
which has no equivalent of TED's own CPV-filtered email alert. A procurement consultant,
sales team, or subcontractor watching a specific CPV category otherwise has to check the
portal's own search by hand. These below-threshold notices commonly run 2-6 week
submission windows; a notice missed for even a few days because the portal was only
checked occasionally can mean missing the deadline entirely and losing the contract to a
competitor who was watching the same CPV code from day one.

### Input

A list of CPV codes to watch, and optionally a publication date window.

```json
{
  "cpvCodes": ["72000000"],
  "publishedFrom": "2026-10-01",
  "publishedTo": "2026-10-31",
  "maxResults": 100,
  "maxChecked": 500
}
```

`maxChecked` is a safety cap on how many candidate lots get checked against your CPV
filter. It stops the run even if `maxResults` matches haven't been found yet, e.g. for a
narrow CPV filter with few matches in the date window: the source API's own CPV filter is
a pre-filter only, and this Actor always re-verifies each candidate client-side before
counting it as a match (see NOTES.md), so a run can check more candidates than it ends up
matching.

CPV matching uses hierarchy prefixes: a filter of `72000000` (IT services, division 72)
matches a lot tagged `72212000` (software development) and vice versa.

### Sample output

One row from the dataset, for a lot matching CPV code `72000000`:

```json
{
  "noticeId": "75540d8f-9f3f-4f3c-bc42-a22ee4bf8c89",
  "lotId": "LOT-0000",
  "title": "Entwicklungsdienstleistung OutSystems",
  "cpvCodes": ["72000000"],
  "deadline": "2026-11-06T11:00:00.000Z",
  "publicationDate": "2026-10-07T02:11:18.000Z",
  "publishingEntity": "FITKO (Foederale IT-Kooperation) AoeR",
  "noticeType": "cn-standard",
  "link": "https://oeffentlichevergabe.de/de/search/details?noticeId=75540d8f-9f3f-4f3c-bc42-a22ee4bf8c89"
}
```

### Pricing

Pay per run started, plus per tender lot checked against your CPV filter (not just per
match: checking, not matching, is the real cost driver here, since the dataset has to be
read and parsed regardless of how many lots end up matching). See the Pricing tab for
exact rates.

***

### Deutscher Vergabemonitor (oeffentlichevergabe.de, nach CPV-Code)

Überwacht neue deutsche öffentliche Ausschreibungen auf oeffentlichevergabe.de (dem
Bekanntmachungsservice, Deutschlands nationalem Vergabeportal), gefiltert nach CPV-Code und
Veröffentlichungsdatum.

Was Sie erhalten: einen Datensatz pro passendem Los, mit Bekanntmachungs-ID, Los-ID, Titel,
CPV-Code, Angebotsfrist, Veröffentlichungsdatum, Name der Vergabestelle, Verfahrensart und
einem Link zur offiziellen Bekanntmachung. Keine personenbezogenen Daten. Eine Ausschreibung
mit mehreren Losen erzeugt einen Datensatz pro Los, da einzelne Lose unterschiedliche
CPV-Bereiche und Fristen haben können.

Warum Sie das brauchen könnten: Ausschreibungen unterhalb der EU-Schwellenwerte (die
Mehrheit nach Anzahl) erscheinen nicht bei TED. Sie werden stattdessen auf
oeffentlichevergabe.de veröffentlicht, ohne vergleichbaren CPV-gefilterten Alarmdienst.

Die CPV-Zuordnung erfolgt hierarchisch: ein Filter `72000000` (IT-Dienstleistungen,
Abteilung 72) findet auch ein Los mit Code `72212000` (Softwareentwicklung) und umgekehrt.

Preisgestaltung: noch nicht festgelegt, siehe oben.

# Actor input Schema

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

List of CPV codes to filter by, e.g. \["72000000", "79000000"]. Matches primary and additional CPV codes.

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

ISO date (YYYY-MM-DD). Defaults to 30 days ago.

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

ISO date (YYYY-MM-DD). Defaults to today.

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

Maximum number of matching lot records to output.

## `maxChecked` (type: `integer`):

Maximum number of lot records to check against the CPV filter before stopping, independent of how many actually match. Protects against a narrow CPV filter with a low match rate paginating indefinitely through a large result set.

## Actor input object example

```json
{
  "cpvCodes": [
    "72000000",
    "79000000"
  ],
  "maxResults": 100,
  "maxChecked": 500
}
```

# Actor output Schema

## `matchedLots` (type: `string`):

Per-lot records.

# 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": [
        "72000000",
        "79000000"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("chosen_loafer/german-procurement").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": [
        "72000000",
        "79000000",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("chosen_loafer/german-procurement").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": [
    "72000000",
    "79000000"
  ]
}' |
apify call chosen_loafer/german-procurement --silent --output-dataset

```

## MCP server setup

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

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/yGPROnRd5TvrSLSE1/builds/9bFQSkQNeupUvLLbz/openapi.json