DACH Tenders & Procurement Monitor

Search and monitor public procurement notices in Germany, Austria, and Switzerland through the official TED Search API. 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

{
  "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:

{
  "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

npm install
npm test
npm start

Node.js 20 or newer is required.

Data source and disclaimer

• TED API documentation
• TED Search API

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.