📜 🇪🇺 EU TED Tender & Award Delta Feed — Procurement Watch

Collect official EU procurement notices, link tenders to awards by published identifiers, and monitor award/incumbent changes.

This actor queries the official anonymous TED Search API (Tenders Electronic Daily, api.ted.europa.eu/v3/notices/search, logged-out, no key) and returns normalized tender and award notice records with buyer, CPV, procedure, lot, value, winner, source URL, and observation fields when TED publishes them. Snapshot mode returns current notices. Watch mode seeds a private baseline, then emits procedure-level additions and published award/incumbent changes on later scheduled runs.

Output is one tender_notice row per result; billing is pay-per-event, the value event being one procedure delta (a $0.02 start fee per run, then $0.02 per procedure delta plus one $0.10 source check per run that reads the source). Source: api.ted.europa.eu, ted.europa.eu.

Use cases

Suppliers monitor relevant published opportunities/awards; bid teams maintain tender-to-award records; procurement analysts assemble buyer/CPV histories; agencies watch named markets for newly published result notices; data teams consume an official-source normalized feed.

📊 Sample Output

Real rows from run i3mjQCYTHK8bB0bIp on build 0.1.20 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

run_id	publication_number	notice_identifier	publication_date	form_type	notice_type
i3mjQCYTHK8bB0bIp	642239-2026	bbf29325-2a93-4503-ba10-3e690b6ed326	2026-09-17	competition	cn-standard
i3mjQCYTHK8bB0bIp	642417-2026	615245bc-b967-4cc4-a7e0-fe4a9e6d6b81	2026-09-17	competition	cn-standard
i3mjQCYTHK8bB0bIp	640156-2026	0783c08d-e79f-414b-b432-aab6ec8f9cfe	2026-09-17	competition	cn-standard
i3mjQCYTHK8bB0bIp	639490-2026	572b3a76-21ca-4b11-b5ed-a8814279a8c2	2026-09-17	competition	cn-standard
i3mjQCYTHK8bB0bIp	641780-2026	c614a2d5-b579-49c9-a5d0-74dfdf3950bb	2026-09-17	competition	cn-standard
i3mjQCYTHK8bB0bIp	642475-2026	222801b5-ecfd-44c6-9bd1-f4624ded3631	2026-09-17	competition	cn-standard
i3mjQCYTHK8bB0bIp	641039-2026	28fd12da-23c4-4cd9-98f2-af65bad28b0c	2026-09-17	competition	cn-standard
i3mjQCYTHK8bB0bIp	641943-2026	f6a71454-2a80-45d3-8678-f296af56c6d8	2026-09-17	competition	cn-standard

The run finished with the status message: CAPPED: reason=CAPPED_MAX_ITEMS; records=50; api_total=393

✅ What you get

One of four record types, discriminated by record_type: tender_notice, award_notice, procedure_delta, or source_receipt.

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_type (string) — Discriminator.
• run_id (string) — Apify run id that produced this item.
• source_url (string) — Exact public request URL or endpoint supporting this item.
• observed_at (string) — RFC3339 UTC time after shape validation.
• publication_number (string/null) — TED publication number; primary source identity for notice records.
• notice_identifier — e.g. bbf29325-2a93-4503-ba10-3e690b6ed326
• notice_version — e.g. 2
• publication_date (string/null) — ISO publication date.
• notice_title (string/null) — Preferred-language notice title.
• form_type (string/null) — TED form type; result maps to award_notice, others to tender_notice.
• notice_type — e.g. cn-standard
• procedure_identifier (string/null) — Official procedure identifier when TED publishes it.
• procedure_key (string/null) — procedure_identifier when present, else publication:{publication_number}.
• internal_procedure_identifier — e.g. P1025
• buyer_names (array/null) — Buyer names (may be empty).
• buyer_identifiers — e.g. ["991-07335-68"]
• buyer_countries (array/null) — Buyer country codes.
• buyer_cities — e.g. ["Bonn"]
• cpv_codes (array/null) — CPV classification codes.
• main_cpv_code — e.g. 72000000
• contract_nature — e.g. services
• procedure_type — e.g. open
• procedure_title — e.g. Projekt 1025 "CSP Update, Evaluierung, Rezertifizierung und API (CUERA)"
• procedure_description — e.g. Um seinen gesetzlichen Verpflichtungen (§146a AO und KassenSichV) nachzukommen m
• deadline — e.g. 2026-10-05
• lot_ids — e.g. ["LOT-0001", "LOT-0002", "LOT-0003"]
• lot_titles — e.g. ["Los 1: „Anpassung und Aktualisierung des CSP-Schutzprofils und CSPL-Schutzprof
• estimated_value (number/null) — Estimated procedure value in source currency.
• estimated_currency — e.g. EUR
• notice_url (string/null) — Public TED notice detail URL.
• content_hash (string/null) — 64-char SHA-256 over canonical mutable fields.
• raw — null in every sample row
• raw_truncated — e.g. False
• winner_names (array/null) — Award winner names (award_notice only; may be empty).
• winner_identifiers (array/null) — Award winner identifiers (award_notice only).
• incumbent_keys (array/null) — Deterministic incumbent keys derived from winner identifier or casefolded name.
• award_value (number/null) — Award value in source currency (award_notice only).
• award_currency (string/null) — Award currency (award_notice only).
• linked_tender_publication_numbers (array/null) — Prior baseline notices with same non-null procedure_identifier (award_notice only).
• delta_type (string/null) — procedure_delta only.
• prior_publication_numbers (array/null) — procedure_delta: prior notices under the same procedure.
• changed_fields (array/null) — procedure_delta: sorted changed field names.
• winner_after (array/null) — procedure_delta: incumbent keys after the change.
• terminal (string/null) — source_receipt only.
• reason_code (string/null) — Stable terminal reason code.
• api_total (integer/null) — source_receipt: TED totalNoticeCount for the query.
• shape_canary_passed (boolean/null) — source_receipt: whether the source-shape canary passed.

Output record types

• tender_notice / award_notice — one normalized notice each (award = TED form-type=result), with publication_number, procedure_key, buyer/CPV, values, winners, content_hash, source_url, observed_at.
• procedure_delta — watch-mode change: new_opportunity, notice_updated, award_published (with prior_publication_numbers, winner_after), etc.
• source_receipt — always pushed, never billed: terminal (NORMAL/GENUINE_EMPTY/PARTIAL/BLOCKED), reason, counts, canary flag.

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "queryMode": "structured",
  "structuredQuery": {
    "cpvCodes": [
      "72000000"
    ],
    "buyerCountries": [
      "DEU"
    ],
    "noticeKinds": [
      "opportunity"
    ]
  },
  "watchMode": false,
  "language": "ENG",
  "maxItems": 50,
  "linkAwards": true
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 50 × $0.004 tender_notice + 0 × $0.006 award_notice + 0 × $0.02 procedure_delta + 1 × $0.10 source_check = $0.32 on the Free tier — snapshot preview rows are delivered unbilled; only the source check and the start fee were charged.

2. A smaller, narrowed run

{
  "queryMode": "structured",
  "structuredQuery": {
    "cpvCodes": [
      "72000000"
    ],
    "buyerCountries": [
      "DEU"
    ],
    "noticeKinds": [
      "opportunity"
    ]
  },
  "watchMode": false,
  "language": "ENG",
  "maxItems": 5,
  "linkAwards": true
}

Caps the run at 5 rows; same billing shape as the sample run above.

3. Watch mode on a schedule

{
  "queryMode": "structured",
  "structuredQuery": {
    "cpvCodes": [
      "72000000"
    ],
    "buyerCountries": [
      "DEU"
    ],
    "noticeKinds": [
      "opportunity"
    ]
  },
  "watchMode": true,
  "language": "ENG",
  "maxItems": 50,
  "linkAwards": true
}

The first run seeds a private baseline and emits zero deltas; every later run emits one row per change, billed at $0.02 each plus the $0.10 source check.

🧾 JSON sample record

One real record from run i3mjQCYTHK8bB0bIp, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_type": "tender_notice",
  "schema_version": "1.0",
  "run_id": "i3mjQCYTHK8bB0bIp",
  "source_url": "https://api.ted.europa.eu/v3/notices/search",
  "observed_at": "2026-09-17T17:15:47Z",
  "publication_number": "642239-2026",
  "notice_identifier": "bbf29325-2a93-4503-ba10-3e690b6ed326",
  "notice_version": "2",
  "publication_date": "2026-09-17",
  "notice_title": "Germany – IT services: consulting, software development, Internet and support – Projekt 1025 \"CSP Update, Evaluierung, Rezertifizierung und API (CUERA)\"",
  "form_type": "competition",
  "notice_type": "cn-standard",
  "procedure_identifier": "73e9d2f3-1b5b-4a5d-aa7c-d5dfb7f1480b",
  "procedure_key": "73e9d2f3-1b5b-4a5d-aa7c-d5dfb7f1480b",
  "internal_procedure_identifier": "P1025",
  "buyer_names": [
    "Bundesamt für Sicherheit in der Informationstechnik"
  ],
  "buyer_identifiers": [
    "991-07335-68"
  ],
  "buyer_countries": [
    "DEU"
  ],
  "buyer_cities": [
    "Bonn"
  ],
  "cpv_codes": [
    "72000000"
  ],
  "main_cpv_code": "72000000",
  "contract_nature": "services",
  "procedure_type": "open",
  "procedure_title": "Projekt 1025 \"CSP Update, Evaluierung, Rezertifizierung und API (CUERA)\"",
  "procedure_description": "Um seinen gesetzlichen Verpflichtungen (§146a AO und KassenSichV) nachzukommen muss das BSI die Schutzprofile BSI-CC-PP-0104 Cryptographic Service Provider (CSP) und BSI-CC-PP-0111 CSPLight (CSPL) aktualisieren. Hierzu sollen im Projekt die",
  "deadline": null,
  "lot_ids": [
    "LOT-0001",
    "LOT-0002",
    "LOT-0003"
  ],
  "lot_titles": [
    "Los 1: „Anpassung und Aktualisierung des CSP-Schutzprofils und CSPL-Schutzprofils (Update-CSPL)“",
    "Los 2: „Evaluierung CSP-PP/CSPL-PP (Eval-CSPL)“",
    "Los 3: „Standardisierte Schnittstellenbeschreibung (API-CSPL)\""
  ],
  "estimated_value": null,
  "estimated_currency": null,
  "notice_url": "https://ted.europa.eu/en/notice/-/detail/642239-2026",
  "content_hash": "3d7e1115ca21e3da89aec6bcf21ac2d6f3657b46abded0a0f43ba25f0b9412f9",
  "raw": null,
  "raw_truncated": false
}

🔧 How it works

Source. The actor reads api.ted.europa.eu, ted.europa.eu — endpoints: https://api.ted.europa.eu/v3/notices/search, https://ted.europa.eu/en/notice. Public pages and feeds only; nothing behind a login.

Transport. Plain HTTPS from the Apify platform, no proxy.

Watch semantics. Snapshot mode (watch_mode: false) returns a preview. Watch mode keys every record on a source-native id, stores a private baseline in a named key-value store, and on each later run emits one delta row per change (new / changed / removed). A blocked fetch is never diffed, so a source outage cannot show up as a mass removal.

Terminal states. A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

Charging. Each procedure delta is charged at the moment it is pushed (procedure_delta); a row that fails to charge is not delivered, so the dataset count always equals the charged count. One source_check is charged per run that actually read the source.

Honest limits

Linking uses official procedure/lot identifiers only and may remain empty; TED documents missing winner data in some results; values stay in original currency; the actor does not infer cancellation, hidden bids, supplier performance, or contract intent; live queries are bounded to 366 days / 5,000 items; only published notices are accessible; outages/blocks/drift fail loud.

Compliance

Official public, logged-out published notices only; no login, CAPTCHA defeat, private/licensed source, or always-on process; the actor stops on objection. Buyers remain responsible for lawful use.

Preview vs Watch mode

• Preview / snapshot (watchMode = false): returns the current tender/award notices for the query and bills one tender_notice / award_notice per emitted record. One-off pull; keeps no baseline.
• Watch (watchMode = true): seeds a private baseline on the first run (zero deltas, no per-record billing), then on later runs emits only qualified procedure_delta rows against that baseline. A zero-delta poll over a complete/CAPPED read charges a single source_check; active runs bill via procedure_delta and are not double-charged. source_receipt diagnostics go to the RUN_RECEIPT key-value record and the log — never the dataset, never billed.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

⏰ Set it on a schedule

A single run is a snapshot. The value is the feed: open the actor in Apify Console → Schedules → Create new, add this actor with input 3 above (watch_mode: true), and pick a cadence:

• Daily — 0 7 * * * (07:00 UTC): catch changes within a day.
• Weekly — 0 7 * * 1: a Monday digest.

Each run is independent; keep the same input on the schedule so the results stay comparable. Schedules can also POST results to a webhook (Console → Integrations).

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Tender notice (tender_notice)	$0.004	$0.0036	$0.0032	$0.0027
Award notice (award_notice)	$0.006	$0.0054	$0.0048	$0.004
Procedure delta (procedure_delta)	$0.02	$0.02	$0.02	$0.01
Source check (source_check)	$0.10	$0.09	$0.08	$0.07

Worked at the live Free-tier price (watch mode, one delta per change):

• 8 procedure deltas: $0.02 start + $0.10 source check + 8 × $0.02 = $0.28
• 25 procedure deltas: $0.02 start + $0.10 source check + 25 × $0.02 = $0.62
• 500 procedure deltas: $0.02 start + $0.10 source check + 500 × $0.02 = $10.12

A run that delivers zero rows charges the $0.02 start fee plus the $0.10 source check (the source was read and reported empty). A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 512 MB.

Yield on the sample run: CAPPED: reason=CAPPED_MAX_ITEMS; records=50; api_total=393. maxItems is a hard ceiling on what is delivered and billed, never a target.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by api.ted.europa.eu, ted.europa.eu. It collects only what the source publishes to any visitor, identifies itself, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (api.ted.europa.eu, ted.europa.eu) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input (in watch mode the first run always seeds the baseline and returns zero deltas); BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee plus one source check.

Q: How many rows can one run return?
A: Up to maxItems (default 500). Raise the cap for a bigger run; you pay per delivered row.

Q: What does watch mode remember between runs?
A: A private baseline of source-native record ids in a named key-value store. Each later run diffs the live source against it and emits only changes.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs except the watch baseline. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other public procurement watches actors?
A: Same output shape and billing model; this one covers api.ted.europa.eu, ted.europa.eu. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Status says CAPPED → your cap (maxItems) was reached → raise it for a bigger run.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
• First watch run shows no deltas → expected: it seeds the baseline; changes appear from the second run.

🔗 Related Actors

• 🇦🇺 AusTender Award Watch — Who Won Which Federal Contract — Watch Australian federal contract awards from the official AusTender OCDS API: who won which contract, for how much, and when an incumbent is replace…
• 🇨🇦 CanadaBuys Tender Watch — Federal Opportunities & Awards — Watch Government of Canada procurement from the official CanadaBuys open data: new and amended tender opportunities and awards by buyer, province and…
• 🇸🇬 Singapore GeBIZ Tender & Award Change Watch — Monitor public Singapore GeBIZ listings and get structured, seed-zero deltas when tenders open, change, close, are cancelled, or publish an award sta…
• Japan Government Procurement Notice Watch (Procurement Portal) — Japanese central-government procurement notices from the government's own Procurement Portal (調達ポータル), read through its English WTO-covered search: c…
• UK Contracts Finder Contract Award & Incumbent Win Watch — Auditable deltas on UK Contracts Finder — new contract awards and incumbent wins, keyed to the notice id. Facts-only, seed-zero, one receipt per run
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.