German Public Infrastructure Tender Monitor

Find German public infrastructure procurement opportunities using strong infrastructure CPV families, topic signals, buyer, geography, deadline, and official evidence links. Infrastructure suppliers, utilities, engineering firms, public-works contractors, and bid teams. Filter public procurement opportunities to relevant infrastructure work and retain the buyer, deadline, CPV match reason, and official notice URL.

What it does

This Actor normalizes the supported evidence into a default Apify dataset and keeps the original source reference with each buyer-visible result. Its buyer-value event is qualified-tender; it uses Apify pay-per-event pricing, so inspect the current Pricing tab and begin with a small validation run.

Supported sources and boundary

• TED Search API public procurement notices
• buyer-supplied public or authorized tender URLs

Only the sources and buyer inputs listed above are supported. The Actor does not bypass login, CAPTCHA, paywalls, robots restrictions, private APIs, or any other access control. It is an independent tool and is not affiliated with the named source platforms or authorities.

Inputs

• watchlistTerms — Optional infrastructure topics, regions, buyers, or CPV interests.
• maxItems — Maximum qualified notices to return.
• startUrls — Optional public or authorized tender URLs.

Existing saved-task fields remain accepted for backward compatibility. Use Apify's maximum run-charge limit for any live validation run.

Buyer-ready output

• title
• buyerName
• deadline
• region
• cpvCodes
• matchReason
• sourceUrl
• confidence
• retrievedAt

Every output preserves source provenance where the input or public source provides it. Unsupported sources return an explicit boundary error instead of an invented record.

First run

{
    "sourceMode": "sample",
    "watchlistTerms": [
        "energy infrastructure"
    ],
    "maxItems": 1
}

The bundled first-run example is a labelled deterministic demonstration, not proof of current live coverage:

{
    "evidenceType": "deterministic_demo",
    "title": "Illustrative energy-network infrastructure tender",
    "buyerName": "Illustrative public buyer",
    "cpvCodes": [
        "45200000"
    ],
    "matchReason": "Strong infrastructure CPV and energy-network topic match"
}

API, dataset, schedules, and webhooks

Use the Apify API or default dataset for programmatic retrieval. Save an input as an Apify task to schedule recurring runs. If the current input schema exposes webhookUrl, it can notify a buyer-controlled endpoint after a completed run; otherwise use Apify webhooks for the task or run.

Common use cases

• Build a source-linked internal review queue.
• Compare repeated signals across a buyer watchlist.
• Export normalized JSON or CSV for an approved downstream workflow.

Limitations and responsible use

Generic words such as public, work, construction, access, or building do not qualify a notice. Flooring, furniture, supplies, unrelated maintenance, and non-infrastructure construction are excluded unless evidence contains the advertised infrastructure scope.

Support

Include the Actor run ID, the input field names (not secrets), an example source URL when authorized, and the observed output field when contacting Zentra support. Check the current Pricing and API tabs before production-scale runs.