TED EU Tenders API

Search published European public-procurement notices through the official TED Search API v3.

The Actor uses TED's anonymous Search API, so it does not require a TED account or API key. It does not use a browser or proxy.

Deterministic traversal

The Actor accepts a TED expert-search filter in filterQuery, but deliberately does not accept a custom sort clause. It appends:

SORT BY publication-number DESC

and traverses results with TED's official ITERATION pagination mode.

This design follows live stability evidence: publication-date ordering can contain large tied cohorts, while publication-number ordering produced repeatable first pages and repeatable multi-page traversals in the private determinism benchmark.

Input

• filterQuery — TED expert-search filter, without SORT BY.
• maxResults — maximum unique notices written to the Dataset, from 1 to 1000.
• pageSize — ITERATION page size, from 10 to the official maximum of 250.
• scope — ALL or ACTIVE.

Example:

{
  "filterQuery": "PD>=20260901",
  "maxResults": 200,
  "pageSize": 100,
  "scope": "ALL"
}

Output

Each Dataset row is one normalized TED notice with:

• publication number and date,
• title,
• buyer names,
• buyer countries,
• CPV codes,
• tender deadlines when present,
• a direct TED detail URL.

The run summary reports the effective deterministic query, API-call count, exact result bound, field coverage, and token traversal metadata.

Data source

This Actor uses the official TED Search API v3 at api.ted.europa.eu. Published-notice search is openly accessible and targeted at data reusers. TED's ITERATION mode supports token-based traversal without the 15,000-document cap that applies to PAGE_NUMBER mode; individual pages are still bounded by TED's per-page limit.

The Actor itself additionally caps customer output at 1,000 notices per run for predictable runtime and resource usage.

Caveats

Deadlines are not present on every published notice. Some fields can contain multiple values, so buyers, countries, CPV codes, and deadlines are normalized as arrays.

TED expert-query syntax is passed to the official API after the Actor verifies that the user has not supplied a custom SORT BY. Invalid expert filters are rejected by TED rather than silently rewritten.

Pricing and billing

This Actor uses Apify pay-per-event pricing.

The primary result event is tender-result. One event corresponds to one normalized TED notice successfully written to the default Dataset. The synthetic apify-actor-start event is charged by the platform at run start.

The Actor uses Apify's event-specific charging manager and stops emitting results if the event charge limit is reached.