# EU Public Procurement (TED) Scraper (`ruph/eu-procurement-ted-scraper`) Actor

Normalized JSON for EU public tender notices from TED. Resolves buyer names and award winners that most tools leave as internal IDs, and keeps every language variant of titles and descriptions. Bulk daily packages or filtered search by country, CPV code and date.

- **URL**: https://apify.com/ruph/eu-procurement-ted-scraper.md
- **Developed by:** [Yaroslav Grebens](https://apify.com/ruph) (community)
- **Categories:** Lead generation, Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## EU Public Procurement (TED) Scraper

Turns EU tender notices into clean, normalized JSON.

Every EU public contract above certain thresholds is published to TED
(Tenders Electronic Daily) as eForms XML. The data is public, but the raw
format is difficult: multilingual fields repeated per language, buyers and
award winners referenced only by internal IDs, and several different document
families sharing the same namespace.

This Actor resolves all of that.

### What makes it different

**Buyer names are resolved.** A notice references its buyer as `ORG-0001`.
This Actor follows the reference into the organization index and returns the
actual name, country, NUTS region and national registration number.

**Award winners are resolved.** This needs a two-step join: the award points
at a tendering-party ID, which points at an organization ID, which points at
the name. Most tools return the raw ID.

**All languages are kept.** A notice title exists once per language.
`title_by_language` gives you all of them; `title` gives you the best single
one.

### Output

```json
{
  "notice_id": "503229-2026",
  "notice_type": "can-standard",
  "title": "Air conditioning renovation works",
  "title_by_language": {
    "FRA": "Travaux de rénovation de la climatisation",
    "ENG": "Air conditioning renovation works"
  },
  "published_date": "2026-07-03",
  "deadline": null,
  "buyer": {
    "name": "DSNA-DTI",
    "country": "FRA",
    "nuts": "FRJ23",
    "city": "Toulouse",
    "national_id": "12006401900074"
  },
  "cpv_main": "45331000",
  "cpv_codes": ["45331000"],
  "lots": [ ... ],
  "awards": [
    {
      "lot_id": "LOT-0001",
      "supplier_name": "SAS Bobion et Joanin",
      "supplier_country": "FRA",
      "value": 3278000.0,
      "currency": "EUR"
    }
  ],
  "source_url": "https://ted.europa.eu/en/notice/-/detail/503229-2026",
  "_completeness": 1.0
}
```

### Modes

**Bulk** — download whole daily packages by OJ S issue number. Fast and
complete; one package is roughly 3,400 notices. Use this for daily sync.

**Search** — filtered query by country, CPV code, keyword or date range.

### Notes on the data

`deadline`, `estimated_value` and `currency` are present on roughly 40% of
notices. That is not a gap in the parser: prior information notices, buyer
profiles and already-awarded notices legitimately do not carry them.

`awards` appears on award notices only, which is about half of a typical day.

Records with `"format": "unsupported"` are non-procurement eForms documents
that TED includes in daily packages (business registration notices and
similar). They are skipped automatically.

# Actor input Schema

## `mode` (type: `string`):

bulk = download whole daily packages (fast, complete). search = filtered query.

## `ojNumbers` (type: `array`):

Format {yyyy}{nnnnn}, e.g. 202600138 for S 138/2026. Find them at ted.europa.eu XML bulk download.

## `countries` (type: `array`):

ISO 3-letter codes, e.g. PRT, DEU, FRA

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

e.g. 72000000 for IT services

## `keywords` (type: `array`):

Free-text terms to match in the notice, e.g. 'software', 'consultoria'

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

Only notices published on or after this date (search mode).

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

Only notices published on or before this date (search mode).

## `rawQuery` (type: `string`):

Overrides the filters above.

## `minCompleteness` (type: `string`):

Filter out sparse records. 0 keeps everything.

## `maxItems` (type: `integer`):

Stop after this many notices. Each one is charged, so this is your budget cap.

## Actor input object example

```json
{
  "mode": "bulk",
  "ojNumbers": [
    "202600147"
  ],
  "minCompleteness": "0",
  "maxItems": 50
}
```

# Actor output Schema

## `notices` (type: `string`):

One record per notice: multilingual titles, resolved buyer, lots and resolved award winners.

## `runSummary` (type: `string`):

Counts for the run: pushed, failed, unique and skipped 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 = {
    "ojNumbers": [
        "202600147"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ruph/eu-procurement-ted-scraper").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 = { "ojNumbers": ["202600147"] }

# Run the Actor and wait for it to finish
run = client.actor("ruph/eu-procurement-ted-scraper").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 '{
  "ojNumbers": [
    "202600147"
  ]
}' |
apify call ruph/eu-procurement-ted-scraper --silent --output-dataset

```

## MCP server setup

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

```

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/fWQFgEafncNdkPA9a/builds/ypSDhhEERBq1gtbuz/openapi.json
