/ted/notices

POST /api/ted/notices

Price: 1 credit

Get an EU public procurement notice by its publication number

How to use it

Get full details of a single EU public procurement notice (tender, contract award, or prior information notice) by its publication number (NNNNNNNN-YYYY). Returns the notice title, publication date, buyer name and country, notice and procedure type, CPV product codes, total awarded value and currency, submission deadline, winning bidders and their countries, and direct links to the official XML, PDF, and HTML documents.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• notice string required — Notice publication number in NNNNNNNN-YYYY format (examples: "196826-2016", "400900-2026")

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 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit 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 — Notice not found 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 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 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 Wait at least 30 seconds, then retry.

Response 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.