# Eu Ted Tender Summary (`worthwhile_loblolly/eu-ted-tender-summary`) Actor

- **URL**: https://apify.com/worthwhile_loblolly/eu-ted-tender-summary.md
- **Developed by:** [rx d](https://apify.com/worthwhile_loblolly) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.80 / 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.

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 Public Tender Summary

Search and summarize **EU public procurement notices** from [TED — Tenders Electronic Daily](https://ted.europa.eu/) via the official **TED Search API**, into a clean Apify dataset.

This Actor calls `POST https://api.ted.europa.eu/v3/notices/search` only (with an official fallback host). It does **not** scrape HTML, bypass captchas, log in, or access private data.

### Features

- Keyword full-text search (`FT~`) plus filters: buyer country, CPV, notice type, procedure, contract nature
- Publication date range (`YYYYMMDD`)
- Automatic pagination (TED max 250 / page; default **ITERATION** scroll mode)
- Flat summary rows: title, buyer, country, deadline, CPV, notice / PDF / XML links
- Multilingual TED fields normalized to a preferred language (English first)
- Run summary stored as key-value record `OUTPUT_SUMMARY`

### Input

| Field | Type | Description |
| --- | --- | --- |
| `keyword` | string | Full-text keyword (`FT~`) |
| `query` | string | Raw TED expert query (AND-combined with filters) |
| `buyerCountry` | string | ISO 3166-1 alpha-3, e.g. `DEU`, `FRA` |
| `cpv` | string | CPV code digits (hierarchical) |
| `noticeType` | string | e.g. `cn-standard`, `can-standard` |
| `procedureType` | string | e.g. `open`, `restricted` |
| `contractNature` | string | `services` / `supplies` / `works` |
| `publicationDateFrom` / `publicationDateTo` | string | `YYYYMMDD` bounds |
| `scope` | string | `ACTIVE` (default) or `ALL` |
| `limit` | integer | Max notices (1–5000, default 50) |
| `paginationMode` | string | `ITERATION` (default) or `PAGE_NUMBER` |
| `linkLanguage` | string | Preferred HTML/PDF language code (`ENG`, …) |

#### Example input

```json
{
  "keyword": "food",
  "noticeType": "cn-standard",
  "publicationDateFrom": "20260901",
  "limit": 50,
  "paginationMode": "ITERATION",
  "linkLanguage": "ENG"
}
```

### Output

Each dataset item is one notice summary, including:

`publication_number`, `ojs_number`, `notice_title`, `buyer_name`, `buyer_country`, `publication_date`, `deadline_date`, `notice_type`, `procedure_type`, `contract_nature`, `cpv_primary`, `cpv_codes`, `place_of_performance`, `estimated_value_lot`, `notice_url`, `pdf_url`, `xml_url`, `fetched_at`, `source`, `source_api`.

A summary is stored as key-value record `OUTPUT_SUMMARY`.

### Use cases

- Export opportunity monitoring for suppliers and exporters
- Daily / weekly tender digests by CPV or country
- Compliance and market-research pipelines
- Downstream enrichment for CRM / AI / RAG tools

### Compliance & attribution

- Data source: [TED (Publications Office of the EU)](https://ted.europa.eu/)
- API docs: [Search API](https://docs.ted.europa.eu/ODS/latest/reuse/search-api.html) · [Developers’ corner](https://ted.europa.eu/en/simap/developers-corner-for-reusers)
- [Legal notice](https://ted.europa.eu/en/legal-notice)
- The Search API is documented as **openly accessible without authentication** for published notices. This Actor only requests public fields returned by that API.
- Not legal advice. Always verify the original notice before bidding. Results may be incomplete or delayed.
- Polite retries on HTTP 429/5xx; small delay between pages.

### Pricing (suggested)

Recommended monetization: **Pay-per-event (PPE)** — rental is sunset for new Actors.

Suggested events:

| Event | Suggested FREE-tier price | Notes |
| --- | --- | --- |
| `apify-actor-start` | `$0.00005` (platform default) | Covers first seconds of compute |
| `apify-default-dataset-item` | **`$0.0012` – `$0.0025`** per notice | ~`$1.20`–`$2.50` per 1,000 notices |

Tender summaries are higher-intent B2B than generic open data; start near **`$0.0018` / result**, offer ~10% off Silver and ~20% off Gold vs FREE, then adjust after real usage.

### Changelog

#### 1.0.1

- Wire Apify Output schema (`.actor/output_schema.json`) so Store publishing can detect run output

#### 1.0.0

- Initial release: TED Search API query, filters, iteration pagination, structured notice summaries

# Actor input Schema

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

Optional raw TED expert-search expression. Combined with structured filters using AND. Example: notice-type=cn-standard AND buyer-country=DEU

## `keyword` (type: `string`):

Full-text keyword searched with TED FT~ operator across notice text. Example: software OR logistics

## `buyerCountry` (type: `string`):

Filter by buyer country code used on TED, e.g. DEU, FRA, ITA, ESP, POL, NLD, BEL.

## `cpv` (type: `string`):

Common Procurement Vocabulary code (digits). Hierarchical — a short prefix matches the branch. Example: 03000000 (food/agricultural) or 72000000 (IT).

## `noticeType` (type: `string`):

TED notice-type filter (eForms).

## `procedureType` (type: `string`):

Procurement procedure filter.

## `contractNature` (type: `string`):

Main contract nature.

## `publicationDateFrom` (type: `string`):

Inclusive lower bound on publication-date, e.g. 20260901.

## `publicationDateTo` (type: `string`):

Inclusive upper bound on publication-date, e.g. 20261231. Leave empty for no upper bound.

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

ACTIVE = currently published notices; ALL = broader TED scope when supported.

## `limit` (type: `integer`):

Maximum number of notice summaries to return (1–5000). TED allows max 250 per request; this Actor pages automatically (ITERATION mode by default).

## `page` (type: `integer`):

1-based page index when paginationMode is PAGE_NUMBER. Ignored in ITERATION mode.

## `paginationMode` (type: `string`):

ITERATION (recommended): scroll through all matching notices with a token. PAGE_NUMBER: classic pages (TED caps at ~15,000 notices).

## `linkLanguage` (type: `string`):

ISO-ish TED language code for notice HTML/PDF links (ENG, DEU, FRA, …).

## Actor input object example

```json
{
  "query": "",
  "keyword": "food",
  "buyerCountry": "",
  "noticeType": "cn-standard",
  "procedureType": "",
  "contractNature": "",
  "publicationDateFrom": "20260901",
  "publicationDateTo": "",
  "scope": "ACTIVE",
  "limit": 50,
  "page": 1,
  "paginationMode": "ITERATION",
  "linkLanguage": "ENG"
}
```

# Actor output Schema

## `results` (type: `string`):

Default dataset items: one row per TED public procurement notice summary.

## `summary` (type: `string`):

Key-value store record OUTPUT_SUMMARY with counts, query, and source attribution.

# 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": "",
    "keyword": "food",
    "buyerCountry": "",
    "publicationDateFrom": "20260901",
    "publicationDateTo": "",
    "limit": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("worthwhile_loblolly/eu-ted-tender-summary").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": "",
    "keyword": "food",
    "buyerCountry": "",
    "publicationDateFrom": "20260901",
    "publicationDateTo": "",
    "limit": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("worthwhile_loblolly/eu-ted-tender-summary").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": "",
  "keyword": "food",
  "buyerCountry": "",
  "publicationDateFrom": "20260901",
  "publicationDateTo": "",
  "limit": 50
}' |
apify call worthwhile_loblolly/eu-ted-tender-summary --silent --output-dataset

```

## MCP server setup

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

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/WbyfqJmNLCvl0Em0f/builds/3y3S2MmObMUGY1cmJ/openapi.json