Skip to content
Torhy

The TED Search API explained for suppliers

Nov 7, 2026

If you sell to the public sector in Europe, sooner or later you will want to search TED more precisely than the website's simple search allows — by CPV branch, by buyer country, by publication window, across many saved queries. The TED Search API is the official way to do that. This article explains what it offers in supplier terms, and how Torhy lets you use it from Claude without writing code.

The essentials

According to the official documentation:

  • The endpoint is POST https://api.ted.europa.eu/v3/notices/search.
  • No authentication is required for searching published notices.
  • A request has a query (in the expert search language) and the list of fields you want back; optional parameters control paging (page, limit), the scope and the pagination mode.
  • Limits: up to 250 notices per page. In page-number mode a query can reach at most 15,000 notices; the iteration (“scroll”) mode, which uses an iterationNextToken from the previous response, has no such cap.

A minimal request looks like this:

{
  "query": "classification-cpv=45233* AND buyer-country IN (POL) AND PD>=20261101",
  "fields": ["publication-number", "notice-title", "buyer-name", "deadline-receipt-tender-date-lot", "links"],
  "limit": 50,
  "page": 1,
  "scope": "ACTIVE",
  "paginationMode": "PAGE_NUMBER"
}

The response contains notices (each with the requested fields), totalNoticeCount and, in iteration mode, the token for the next page.

The expert query language

TED's help page on search and browse documents the syntax. The parts suppliers use most:

Fields and aliases. You can use full field names or short aliases: PD is the publication date, FT is full text, ND the publication number, PC the CPV classification, RC the place of performance.

Operators.

  • = exact match, ~ contains (for text), IN (...) for a list (implicit OR).
  • >, <, >=, <= for numbers and dates.
  • !=, !~ and NOT IN for exclusions; AND, OR, NOT with parentheses for grouping.

Dates are written YYYYMMDD, and ranges are possible: PD = (20260101 <> 20260131).

Wildcards. * matches any number of characters and ? a single one — handy for CPV branches: classification-cpv=45233* matches every code under road construction and surface works. Wildcards are not allowed inside quoted phrases.

Phrases. Double quotes match an exact phrase: FT~"roof repair".

Sorting. Results can be sorted by keyword or numeric fields, ascending or with DESC.

Example — open notices for medical gloves in the Baltic states:

FT~(gloves) AND classification-cpv=3314142* AND buyer-country IN (EST LTU LVA)
AND deadline-receipt-tender-date-lot>=20261116 SORT BY publication-number DESC

Useful fields for suppliers

Need Field
Notice number publication-number
Title (translations keyed by language) notice-title
Buyer and its country/city buyer-name, buyer-country, buyer-city
What is bought classification-cpv, main-classification-proc
When to bid deadline-receipt-tender-date-lot, deadline-receipt-tender-time-lot
How much estimated-value-proc, estimated-value-cur-proc, estimated-value-lot
Where place-of-performance
Type of notice / procedure notice-type, procedure-type
Documents document-url-lot
Results winner-name, total-value, total-value-cur
Links to HTML/PDF/XML links

Multilingual fields come back as maps keyed by language (for example "eng" for the English title), and lot-level fields come back as lists — your code has to normalise them.

A request, end to end

A search is a POST to https://api.ted.europa.eu/v3/notices/search with a JSON body. The fields that matter in practice:

{
  "query": "FT~(gloves) AND buyer-country IN (EST LTU LVA) AND deadline-receipt-tender-date-lot>=20261116",
  "fields": ["publication-number", "notice-title", "buyer-name", "buyer-country",
             "classification-cpv", "deadline-receipt-tender-date-lot", "links"],
  "limit": 50,
  "page": 1,
  "scope": "ALL",
  "paginationMode": "PAGE_NUMBER"
}
  • fields is required in practice: list only what you will display, because responses grow quickly.
  • limit is capped at 250 notices per page.
  • paginationMode PAGE_NUMBER is fine for browsing the first pages of results; for a full export use ITERATION and pass back the iterationNextToken from each response until no token is returned.
  • scope selects all notices or only the active/latest ones.

The response contains notices (one object per notice with the requested fields, many of them multilingual objects keyed by language code) and totalNoticeCount. Store the publication number as the stable key: it is what the notice URL and every follow-up request use.

Notice types worth knowing

eForms notice types tell you what a notice is. For bidding opportunities you mostly want contract notices such as cn-standard (and cn-social, cn-desg), plus prior information notices used as a call for competition (pin-cfc-standard, pin-cfc-social). Result notices like can-standard show awards. The help page's own example filters by type: notice-type IN (cn-desg can-modif).

Pitfalls

  • Date formats differ between notice generations (2026-11-14+01:00 vs 2026-11-14Z); parse only the date part when you compare.
  • Several deadlines may exist — one per lot. Use the earliest one that is still in the future.
  • Values can be missing at procedure level but present per lot; sum lots if you need a total.
  • Iteration tokens expire, so restart a scroll instead of resuming days later.
  • Rate limits apply. Space out scheduled requests and cache results.

Using it without code

Torhy wraps all of the above into two MCP tools:

  • search_ted turns a request like “open IT services tenders in Germany and Austria, CPV 72, deadline in two weeks or later” into an expert query, runs it (cached for one hour) and returns compact results.
  • get_ted_notice fetches a notice's details — description, lots, document links, contacts — by publication number.

It also ingests competition notices every six hours, so EU alerts work alongside Ukrainian Prozorro alerts.

Find open IT services tenders (CPV 72) in Germany and Austria with a deadline at least two weeks away.

Attribution: © European Union, TED.

Try Torhy today

Connect in two minutes. Free plan, no card required.