/uvo/tenders/search

POST /api/uvo/tenders/search

Price: 20 credits

Search the register of Slovak public procurements kept by ÚVO — above- and below-threshold and low-value procurements — by name, contracting authority name or IČO, CPV, NUTS, contract type, procedure, financial band, award criterion, EU co-financing, defence, EVO use and last update, with the buyer, main CPV, region and last update of each procurement. Most recently updated first.

How to use it

Filters combine with AND. Pass the id of a row to uvo/tenders for the state, CPV and NUTS codes, the procurement's Bulletin notices and its documents; a notice id goes to uvo/notices.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of results (min: 1; max: 500)
• keyword string nullable — Words in the procurement name (examples: "most"; minLength: 2)
• buyer_name string nullable — Words in the contracting authority name (examples: "Bratislava"; minLength: 2)
• buyer_ico string nullable — Contracting authority IČO (examples: "00603481")
• cpv string nullable — CPV code (examples: "45221111-3")
• nuts string nullable — NUTS code of the place of performance (examples: "SK010")
• updated_within string nullable — Last update of the procurement (one of: "last_7_days", "last_31_days", "last_365_days")
• contract_type string nullable — Type of contract (one of: "goods", "services", "works", "summaries")
• procedure_type string nullable — Procurement procedure (one of: "open", "restricted", "negotiated_with_publication", "direct_negotiation", "competitive_dialogue", "design_contest", "unspecified", "concession", "buyer_profile", "dynamic_purchasing_system", "qualification_system", "call_for_tenders", "innovation_partnership")
• value_band string nullable — Financial threshold band (one of: "above_threshold", "below_threshold", "sub_threshold", "low_value")
• award_criterion string nullable — Award criterion (one of: "most_economically_advantageous", "lowest_price")
• eu_funded boolean nullable — Co-financed from EU funds
• defence boolean nullable — Defence or security procurement
• evo_only boolean — Only procurements run in the EVO system (default: false)

Response

• @type string (default: "UvoTenderSummary")
• id string required
• name string nullable
• buyer object nullable
  • @type string (default: "UvoBuyerRef")
  • name string required
  • profile_id string nullable
  • url string nullable
• main_cpv_name string nullable
• region string nullable
• updated_date string nullable
• is_evo boolean 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 — The entity was not found, or a precondition failed 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.