# Eu Ted Tenders Scraper (`real-estate-api/eu-ted-tenders-scraper`) Actor

This Actor collects public procurement notices and contract awards from the EU's Tenders Electronic Daily (TED) portal. It extracts tender titles, publication numbers, CPV codes,contracting authorities, countries, estimated values, and submission deadlines to support bid tracking and market research

- **URL**: https://apify.com/real-estate-api/eu-ted-tenders-scraper.md
- **Developed by:** [real-estate-api](https://apify.com/real-estate-api) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.99 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## EU TED Tenders Scraper

![EU TED Tenders Scraper cover](https://images.bigibyte.com/cdn-cgi/image/width=1260,height=540,fit=cover,format=webp/apify-actors-covers/eu-ted-tenders-scraper-cover.png)

### EU TED Tenders Scraper — European Public Procurement Notices

Collect structured public procurement notices from the European Union's Tenders Electronic Daily (TED) platform. Search for tenders using expert queries, select the notice fields you need, and save the results in an organized dataset for research, monitoring, and analysis.

### What This Actor Does

This actor searches TED for public procurement notices and creates one dataset record per notice.

Depending on the selected fields, records can include publication numbers, multilingual notice titles, buyer names, publication dates, and available notice links. You can filter your search with an expert query and limit the number of collected notices.

### Features

- Search European public procurement notices using expert queries.
- Select the notice fields to include in the dataset.
- Filter notices by keywords, buyer country, and other supported query criteria.
- Collect multilingual notice titles and buyer names when available.
- Retrieve publication numbers, publication dates, and notice links.
- Remove duplicate notices using their publication numbers.
- Set a maximum number of notices per run.
- Export collected data in JSON, CSV, Excel, and other supported dataset formats.

### Collection Mode

**Expert-query Search**

Search TED using an expert query, such as `FT~software` for keyword-based searches or `buyer-country=FRA` for notices associated with buyers in France.

### Input Parameters

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `mode` | String | No | `search` | Selects the collection mode. |
| `query` | String | No | — | TED expert query used to find matching notices. |
| `fields` | Array | No | — | Notice fields to include in the collected records. |
| `scope` | String | No | `ACTIVE` | Defines the notice scope to search. |
| `maxItems` | Integer | No | `50` | Maximum number of notices to collect. Maximum: 1000. |
| `requestDelaySecs` | Number | No | `1` | Delay between requests, in seconds. |

### Example Input

```json
{
    "mode": "search",
    "query": "FT~software",
    "fields": [
        "publication-number",
        "notice-title",
        "buyer-name",
        "publication-date"
    ],
    "scope": "ACTIVE",
    "maxItems": 50,
    "requestDelaySecs": 1
}
```

### What Data Does This Actor Extract?

The actor returns the notice fields selected in the input, along with collection metadata.

| Field | Description |
|---|---|
| `publication-number` | Unique publication number of the notice. |
| `notice-title` | Notice title, potentially available in multiple languages. |
| `buyer-name` | Contracting authority or buyer name, potentially available in multiple languages. |
| `publication-date` | Date when the notice was published. |
| `links` | Available links to the notice, including its HTML page. |
| `scrapedAt` | Date and time when the record was collected. |

The fields returned depend on the selected notice fields and the information available for each notice.

### Example Output

```json
{
    "publication-number": "353060-2016",
    "buyer-name": {
        "eng": "Example contracting authority"
    },
    "publication-date": "2016-10-11+02:00",
    "links": {
        "html": {
            "ENG": "https://ted.europa.eu/en/notice/-/detail/353060-2016"
        }
    },
    "notice-title": {
        "eng": "Business and IT services for enterprise content management"
    },
    "scrapedAt": "2026-10-26T00:00:00+00:00"
}
```

### Use Cases

- **Procurement Monitoring:** Find EU tender opportunities matching specific keywords, sectors, or buyer countries.
- **Market Research:** Analyze procurement activity by collecting notice titles, contracting authorities, and publication dates.
- **Business Development:** Build lists of relevant tender opportunities for sales and business development teams.
- **Historical Research:** Collect a limited set of notices for procurement analysis and reporting.
- **Data Pipelines:** Use structured procurement records in dashboards, monitoring systems, and data enrichment workflows.

### Working with Your Dataset

After the actor finishes running, open its dataset to review the collected notices.

You can export your results in supported formats, including:

- JSON
- CSV
- Excel

These formats make it easier to analyze procurement opportunities, build reports, and use collected records in other data workflows.

### FAQ

**Who is this actor for?**

It is useful for researchers, procurement analysts, consultants, and businesses interested in European public procurement opportunities.

**What search queries can I use?**

You can provide TED expert queries, including keyword searches such as `FT~software` and buyer-country filters such as `buyer-country=FRA`.

**Can I choose which fields to collect?**

Yes. Use the `fields` input to select the notice fields you want in your dataset.

**What is the maximum number of notices per run?**

You can collect up to 1000 notices per run using `maxItems`. The default is 50.

**Can I schedule recurring collections?**

Yes. You can use Apify Schedules to run the actor automatically at your preferred intervals.

**What happens if some notice fields are unavailable?**

The available information can vary between notices. Some selected fields may be missing from individual records.

### Disclaimer

This actor is an independent tool and is not affiliated with, endorsed by, sponsored by, or officially associated with TED or the European Union Publications Office. It collects publicly available procurement information. Users are responsible for ensuring that their use of collected data complies with applicable terms, attribution requirements, and laws.

### Is Web Scraping Legal?

Collecting information that is already public is generally legal. There is no single law that bans all forms of web scraping. The limits are the usual ones: do not break into accounts, do not take private or confidential data, and be careful with personal data and copyrighted works. A site's terms can also restrict how you access it. Facts such as a public name, price, or rating are not the same as republishing someone's article or photo.

This actor collects information from public pages. It does not log in and it does not bypass access controls.

For a longer explanation, see Apify's article [Is web scraping legal?](https://blog.apify.com/is-web-scraping-legal/).

# Actor input Schema

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

What to scrape. Expert-query search posts a TED expert query and returns selected notice fields.

## `query` (type: `string`):

TED expert query syntax (for example FT~software or buyer-country=FRA).

## `fields` (type: `array`):

Notice fields to return from TED.

## `scope` (type: `string`):

ACTIVE, LATEST, or ALL.

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

Stop after this many successful rows. Hard max is 1000.

## `requestDelaySecs` (type: `number`):

Seconds to wait between requests.

## `userAgent` (type: `string`):

User-Agent header sent with each request.

## `timeoutSecs` (type: `integer`):

Overall run budget in seconds.

## `requestTimeoutSecs` (type: `integer`):

Per-request timeout in seconds.

## `proxyConfiguration` (type: `object`):

Optional proxy. Leave off unless you need it.

## Actor input object example

```json
{
  "mode": "search",
  "query": "FT~software",
  "fields": [
    "publication-number",
    "notice-title",
    "buyer-name",
    "publication-date"
  ],
  "scope": "ACTIVE",
  "maxItems": 100,
  "requestDelaySecs": 1,
  "userAgent": "ActorResearch/1.0",
  "timeoutSecs": 300,
  "requestTimeoutSecs": 30,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

Dataset rows in the overview table.

## `dataset` (type: `string`):

Full dataset for this run.

## `items` (type: `string`):

Dataset items as JSON.

# 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 = {
    "query": "FT~software",
    "fields": [
        "publication-number",
        "notice-title",
        "buyer-name",
        "publication-date"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("real-estate-api/eu-ted-tenders-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 = {
    "query": "FT~software",
    "fields": [
        "publication-number",
        "notice-title",
        "buyer-name",
        "publication-date",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("real-estate-api/eu-ted-tenders-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 '{
  "query": "FT~software",
  "fields": [
    "publication-number",
    "notice-title",
    "buyer-name",
    "publication-date"
  ]
}' |
apify call real-estate-api/eu-ted-tenders-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,real-estate-api/eu-ted-tenders-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/xSq0CdJQiagIMDagK/builds/Ay3Mcb3WbzQ5tUleE/openapi.json
