EU TED Tenders & Procurement Leads

Get clean EU TED tenders, public procurement notices, and procurement lead data without building your own Tenders Electronic Daily connector, normalization layer, privacy filter, quality gate, or Parquet pipeline.

This Actor queries the official TED Search API, converts tenders and award notices into a canonical procurement schema, suppresses personal-contact data, validates the batch, and returns CRM-ready records in the default dataset. Optional Parquet artifacts with SHA-256 checksums are written to the run key-value store for analytical workflows.

Why buyers use it

• Official-source TED data via documented API access, not rendered-page scraping.
• One normalized row per EU tender or award notice, with buyer, country, CPV, value, stage, dates, amendment flags, and official-source links.
• Privacy-safe commercial output: personal-contact fields are suppressed before publication.
• Quality report included with every run, so buyers can inspect validation status before using the data.
• Optional deterministic ZSTD Parquet bundle for DuckDB, Polars, pandas, and data-warehouse ingestion.

Common use cases

• Find active sales opportunities by buyer country and CPV segment.
• Discover EU tender leads for software, construction, healthcare, services, and other CPV-defined markets.
• Monitor competitors, buyers, suppliers, frameworks, and amendments.
• Feed procurement leads into CRM, enrichment, BI, and market-sizing workflows.
• Build country or sector watchlists without maintaining TED ingestion code.

Examples and integrations

Public API examples, pandas and DuckDB notebooks, and a CRM import mapping are available at https://github.com/AnasCharfi/eu-ted-procurement-examples.

Input

• dateFrom, dateTo: publication date range, max 31 days.
• country: optional ISO alpha-3 buyer country code, e.g. FRA.
• cpv: optional CPV code or wildcard prefix, e.g. 30*.
• maxResults: hard row cap, max 1,000.
• includeParquet: also produce Parquet files and checksums.

Output

The default dataset contains normalized notice rows. The key-value store contains OUTPUT, QUALITY.json, QUALITY.md, and optional PARQUET_* files.

Every output includes attribution to EU Tenders Electronic Daily (TED) and a clear notice that this is an independent transformed dataset, not an official EU or Publications Office product.

What you get in each row

Each dataset item is one normalized procurement notice designed for search, lead scoring, CRM import, and analytics. Common fields include:

• record_id, source_notice_id, and source_url for traceability back to TED.
• publication_date, deadline fields, and procurement stage.
• buyer_name, buyer_country_code, and normalized buyer identifiers where available.
• Notice title, description summary, CPV code, and procurement category.
• estimated_value and estimated_value_currency when TED publishes value data.
• Amendment and lot-count indicators for workflow triage.
• Retrieval and quality metadata for audit-friendly pipelines.

Personal-contact data is suppressed before records are written to the paid dataset.

Example output

{
  "record_id": "ted:2025/S-150-512345",
  "source_notice_id": "512345-2025",
  "publication_date": "2025-08-04T00:00:00Z",
  "buyer_country_code": "FRA",
  "buyer_name": "Example public buyer",
  "title": "Software development and support services",
  "main_cpv_code": "72000000",
  "estimated_value": "250000",
  "estimated_value_currency": "EUR",
  "procurement_stage": "competition",
  "source_url": "https://ted.europa.eu/..."
}

Field availability depends on what the official TED notice contains. The Actor keeps the schema stable and leaves unavailable values empty instead of inventing data.

Pricing examples

Current launch pricing is pay per result:

• 100 results: about $0.19.
• 1,000 results: $1.90.
• 5,000 results across multiple runs: about $9.50.

The small Actor Start event remains at Apify's default $0.00005, and platform usage is included in the event price.

CRM and BI use cases

• Sales teams can import tender leads into HubSpot, Salesforce, Pipedrive, or a spreadsheet by mapping buyer, country, CPV, deadline, value, and source URL.
• Market-intelligence teams can track demand by country, buyer, and CPV segment.
• RevOps teams can enrich notice rows with account ownership, territory rules, and competitor tags.
• Data teams can load Parquet artifacts into DuckDB, Polars, pandas, BigQuery, Snowflake, or a lakehouse pipeline.

Why official TED API data beats scraping

• More stable than HTML scraping because it uses TED's documented Search API.
• Cleaner provenance: every record links back to the official source.
• Lower operational risk: no browser rendering, CAPTCHA handling, or fragile CSS selectors.
• Better for repeat workflows: deterministic date windows, bounded result caps, quality reports, and optional Parquet outputs.
• Easier compliance review: source attribution and legal boundary are included in every run.

Source and legal boundary

Data is sourced from EU Tenders Electronic Daily (TED), https://ted.europa.eu, and reused under Commission Decision 2011/833/EU on the reuse of Commission documents. This Actor does not use EU or TED logos and does not claim official status, endorsement, or affiliation.

Official notices can be corrected, amended, withdrawn, or updated after publication. This Actor provides transformed data for lead generation, analytics, and workflow triage. It is not legal, procurement, financial, or compliance advice. Always verify current tender and award details at the official TED source before making business, legal, or compliance decisions.