/uvo/tenders

POST /api/uvo/tenders

Price: 20 credits

Get one procurement from the Slovak ÚVO register by its id or URL: name, contracting authority, state, contract type, procedure, every CPV and NUTS code, EU co-financing, defence and e-auction flags, EVO use, creation, publication and last-update times, the procurement's Bulletin notices with type, form and issue, and its published documents. Notices and documents are each capped at 700 rows; an X-Warning header marks a procurement past that cap.

How to use it

Pass the id of a uvo/tenders/search row. Each notice id opens the full eForms notice with lots, values and winners in uvo/notices, and buyer.profile_id opens the contracting authority in uvo/buyers.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• tender string required — Procurement id or register URL (examples: "453542", "https://www.uvo.gov.sk/vyhladavanie/vyhladavanie-zakaziek/detail/453542")

Response

• @type string (default: "UvoTender")
• id string required
• name string required
• buyer object nullable
  • @type string (default: "UvoBuyerRef")
  • name string required
  • profile_id string nullable
  • url string nullable
• status string nullable
• contract_type string nullable
• procedure_type string nullable
• cpvs array (default: [])
  • @type string (default: "UvoCode")
  • code string nullable
  • name string nullable
• nuts array (default: [])
  • @type string (default: "UvoCode")
  • code string nullable
  • name string nullable
• is_eu_funded boolean nullable
• is_defence boolean nullable
• has_electronic_auction boolean nullable
• is_evo boolean nullable
• evo_url string nullable
• created_at integer nullable
• updated_at integer nullable
• published_at integer nullable
• notices array (default: [])
  • @type string (default: "UvoNoticeRef")
  • id string required
  • notice_number string nullable
  • notice_type string nullable
  • form_code string nullable
  • buyer_name string nullable
  • published_date string nullable
  • bulletin_issue string nullable
  • url string nullable
• documents array (default: [])
  • @type string (default: "UvoDocument")
  • id string required
  • document_type string nullable
  • name string nullable
  • buyer_name string nullable
  • published_date string nullable
  • modified_date string nullable
  • url string nullable
• url 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 — No procurement with this identifier in the ÚVO register 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.