# /ted/notices/search

`POST /api/ted/notices/search`

Price: 1 credit

Search EU public procurement notices with full-text and structured filters

## How to use it

Search EU public procurement notices (tenders, contract awards, prior information notices) by full-text keyword, optionally filtered by buyer country, notice type, procurement procedure type, CPV product code, and publication date range. Returns each notice's title, publication date, buyer name and country, notice and procedure type, CPV codes, total awarded value, submission deadline, winning bidders, and links to the official XML, PDF, and HTML documents. Results are newest-first.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `query` (string, required) — Full-text search across the notice content (examples: "cloud", "road construction"; minLength: 1)
- `count` (integer, required) — Number of notices to return (min: 1)
- `country` (string, nullable) — Filter by buyer country (ISO 3166-1 alpha-3 code) (one of: "AUT", "BEL", "BGR", "HRV", "CYP", "CZE", "DNK", "EST", "FIN", "FRA", "DEU", "GRC", "HUN", "IRL", "ITA", "LVA", "LTU", "LUX", "MLT", "NLD", "POL", "PRT", "ROU", "SVK", "SVN", "ESP", "SWE", "NOR", "ISL", "LIE", "CHE", "GBR")
- `notice_type` (string, nullable) — Filter by notice type (one of: "cn-standard", "cn-social", "cn-desg", "can-standard", "can-social", "can-desg", "can-modif", "pin-only", "pin-buyer", "pin-cfc-standard", "pin-cfc-social", "pin-rtl", "veat", "qu-sy", "brin", "subco", "corr")
- `procedure_type` (string, nullable) — Filter by procurement procedure type (one of: "open", "restricted", "neg-w-call", "neg-wo-call", "comp-dial", "innovation", "oth-single", "oth-mult")
- `cpv` (string, nullable) — Filter by CPV product/service code (examples: "72000000", "45233140")
- `published_from` (string, nullable) — Earliest publication date, inclusive (YYYY-MM-DD) (examples: "2024-01-01")
- `published_to` (string, nullable) — Latest publication date, inclusive (YYYY-MM-DD) (examples: "2024-12-31")

## Response

### 200 — Successful Response

- `@type` (string) (default: "TedNotice")
- `id` (string, required)
- `title_proc` (string, nullable)
- `title_lot` (array) (default: [])
- `published_at` (string, nullable)
- `countries` (array) (default: [])
- `buyer_name` (string, nullable)
- `buyer_country` (string, nullable)
- `notice_type` (string, nullable)
- `procedure_type` (string, nullable)
- `cpv_codes` (array) (default: [])
- `total_value` (number, nullable)
- `total_value_currency` (string, nullable)
- `deadline` (string, nullable)
- `winner_names` (array) (default: [])
- `winner_countries` (array) (default: [])
- `links` (object, nullable)
  - `@type` (string) (default: "TedNoticeLinks")
  - `xml` (string, nullable)
  - `pdf` (string, nullable)
  - `html` (string, nullable)

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.

### 412

The entity was not found, or a precondition failed

What to do: Retrying will not help: either the entity does not exist, or the input points at a different one.

### 429

Too many requests: a rate limit or a usage window is exhausted

What to do: When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.

### 500

Something broke on our side

What to do: Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.

### 529

Rate limit reached, or the endpoint is overloaded

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these headers:

- `X-Error` — Error message text (present only on error)
- `X-Request-ID` — Unique request identifier
- `X-Execution-Time` — Execution time in seconds
- `X-Result-Count` — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
- `X-Total-Available-Results` — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
- `X-Warning` — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
- `X-Retry-After` — Seconds to wait before retrying. Present only on 429.