# EU Tender Bid Signals — TED Procurement Records (`nexgensignal/eu-tender-bid-signals`) Actor

Normalized EU procurement bid-signal records from the official TED API — buyer, CPV, deadline, value, awarded organisation, org-level only. No API key. Pay per record. Part of NexGen Signal — official-source data products.

- **URL**: https://apify.com/nexgensignal/eu-tender-bid-signals.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Business, News, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 bid signal records

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/platform/actors/running/actors-in-store#pay-per-event

## 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 Tender Bid Signals — TED Procurement Records

**Official source. No API key. Pay per record.**

This actor turns the EU's Tenders Electronic Daily (TED) into clean, per-notice bid-signal records. Each run queries TED's public v3 API and delivers one normalized record per procurement notice — the buyer (contracting authority), the classification (CPV), the contract nature, the deadline, the value, and the awarded organisation when present — all at the **organisation level only**. It is a decision-record, not a monitor or an alert.

### What this is, in one paragraph

TED publishes hundreds of thousands of EU public-procurement notices. This actor reads them through the official keyless API and flattens each into a single row you can load into a spreadsheet, a CRM, or a pipeline: who is buying, what they are buying (CPV + nature), by when (deadline), for how much, and — on award notices — who won. Multilingual fields are flattened to their published values; nothing is invented or scored. Contact-person fields are never requested, so no individual's data enters the record.

### Who buys this and for what job

- **Bid and capture teams** building a normalized pipeline of relevant EU tenders by sector (CPV) without scraping the TED website.
- **Market-intelligence and BD teams** tracking who is buying and who is winning across EU procurement.
- **Analysts and researchers** who need the structured notice facts with a link back to the official notice.
- **Data engineers** wanting a keyless, one-call feed of EU procurement records for a pipeline.

The job it does: turn published EU procurement notices into normalized org-level decision records — with provenance, and without an account or key.

### Person suppression

TED notices can carry contact-person details. This actor requests and emits **organisation-level fields only** — the record schema has no person, contact, email, or phone field, so individual contact data cannot appear. Verified by the acceptance suite (a notice carrying a person field is ingested and the emitted record contains no person data).

### Pricing

Pay per event. One event: one delivered bid-signal record. Tiered by your Apify plan; delivered before charged. No start fee. Blocked runs and empty results cost nothing.

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `bid_signal_record` | $0.05 | $0.045 | $0.04 | $0.0335 |

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `publishedSince` | string (YYYYMMDD) | first of current month | Return notices published on or after this date. Earlier = more records. |
| `cpvPrefix` | string | — | Optional CPV prefix (2–8 digits) to filter to a sector (e.g. `45` construction, `33` medical). |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per notice. Example from a real award notice:

```json
{
  "record_id": "533445-2026",
  "publication_number": "533445-2026",
  "notice_type": "can-standard",
  "publication_date": "2026-08-03+02:00",
  "title": "Fornitura di dispositivi medici",
  "buyer_name": "ESTAR - Ente di Supporto Tecnico Amministrativo Regionale",
  "buyer_country": "ITA",
  "cpv_codes": ["33190000"],
  "contract_nature": ["supplies"],
  "deadline": null,
  "total_value": null,
  "winner_names": ["HERAEUS S.P.A.", "STRYKER ITALIA S.R.L.", "EUROPA TRADING - S.R.L."],
  "source": "EU TED (Tenders Electronic Daily)",
  "source_url": "https://ted.europa.eu/en/notice/-/detail/533445-2026",
  "licence": "EU TED ... Commission Decision 2011/833/EU ...",
  "attribution": "Source: EU Tenders Electronic Daily (TED)",
  "disclaimer": "Decision-record of a published EU procurement notice (TED) ... not a monitoring, alerting, or bid-writing service ...",
  "observed_at": "2026-08-18T00:00:00Z"
}
```

Every run also writes an unbilled `RUN_RECEIPT` with the robots check, the query, notices seen, delivered, and whether charged equals delivered.

### Cost guidance

One `bid_signal_record` per delivered notice, so cost = notices pulled × your plan's per-record price. 1,000 notices is **$50** (Free) / **$33.50** (Gold); a 500-record default sample is **$25** / **$16.75**.

### Honest limitations

- **It is a decision-record, not a monitor or alert.** It returns the notices matching your window/filter at run time; it does not watch for new ones or notify you.
- **Living source.** TED publishes continuously; re-run to refresh. Notices are as-published (award notices carry winners; contract notices do not).
- **Fields as published.** Multilingual values are flattened to their published strings; nothing is translated or re-derived.
- **Org-level only.** No contact-person data, by construction.

### Differentiation

Distinct from the NexGenData EU-tender products: fleet-1's **eu-ted-tender-monitor** and fleet-2's **ungm-tender-award** watch are monitors/alert feeds. This actor is the **normalized decision-record shape** — one flat org-level row per notice for loading and analysis, not a change-watch or notification. Narrower, specific job: the record, not the alert. It is also the EU counterpart to the NexGen Signal **UK contract opportunity records** actor (UK vs EU).

### The NexGen Signal family

Part of the NexGen Signal family of official-source, pay-per-record products:

- [Eurostat House Price Index](https://apify.com/nexgensignal/eurostat-house-price-index)
- [Eurostat Waste Generation](https://apify.com/nexgensignal/eurostat-waste-generation)
- [Eurostat Waste Treatment](https://apify.com/nexgensignal/eurostat-waste-treatment)
- [Eurostat Business & Consumer Confidence](https://apify.com/nexgensignal/eurostat-business-confidence)
- [Eurostat Income Distribution (EU-SILC)](https://apify.com/nexgensignal/eurostat-income-distribution)
- [Eurostat Construction Production](https://apify.com/nexgensignal/eurostat-construction-production)
- [Eurostat Immigration Statistics](https://apify.com/nexgensignal/eurostat-immigration-statistics)
- [Eurostat Emigration Statistics](https://apify.com/nexgensignal/eurostat-emigration-statistics)
- [Eurostat Road Freight Transport](https://apify.com/nexgensignal/eurostat-road-freight)
- [Organization Sanctions & LEI Risk](https://apify.com/nexgensignal/organization-sanctions-lei-risk)

*Source: EU Tenders Electronic Daily (TED). Reused under the EU reuse policy (Commission Decision 2011/833/EU) with acknowledgement of source; reformatted to org-level records, values unmodified. Contact-person fields excluded.*

# Actor input Schema

## `publishedSince` (type: `string`):

Return notices published on or after this date. Defaults to the first of the current month (a bounded window). Earlier = more records.

## `cpvPrefix` (type: `string`):

Optional CPV classification prefix (2-8 digits) to filter to a sector, e.g. 45 for construction, 33 for medical.

## `maxRecords` (type: `integer`):

Maximum records delivered and billed. You are billed only for records delivered.

## Actor input object example

```json
{
  "publishedSince": "20260801",
  "maxRecords": 500
}
```

# Actor output Schema

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

The delivered EU tender bid-signal 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 = {
    "publishedSince": "20260801",
    "maxRecords": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/eu-tender-bid-signals").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 = {
    "publishedSince": "20260801",
    "maxRecords": 500,
}

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/eu-tender-bid-signals").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 '{
  "publishedSince": "20260801",
  "maxRecords": 500
}' |
apify call nexgensignal/eu-tender-bid-signals --silent --output-dataset

```

## MCP server setup

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

```

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/mmJs3ZuXvVcL1Dqoq/builds/9jMktUc6wT37mSoOD/openapi.json