/uvo/notices

POST /api/uvo/notices

Price: 10 credits

Get one notice from the Slovak public procurement Bulletin (Vestník) by its id or URL: notice number, Bulletin issue and date, notice and form type, the procurement and organisation it belongs to, procedure and version identifiers, reference number, name, description, contract type, main CPV and procedure, every organisation named in it with IČO, address and contacts, and every labelled field of the notice — lots, award criteria, values, tenders received, winners and contract changes — with its section.

How to use it

Pass a notice id from uvo/tenders notices. fields keeps the notice's own Slovak labels with their section and subsection, so a result notice's winners and values sit under its Výsledok section.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• notice string required — Bulletin notice id or URL (examples: "1410610", "https://www.uvo.gov.sk/vestnik-a-registre/vestnik/oznamenie/detail/1410610")

Response

• @type string (default: "UvoNotice")
• id string required
• notice_title string nullable
• notice_number string nullable
• bulletin_issue string nullable
• bulletin_date string nullable
• notice_type string nullable
• form_type string nullable
• notice_subtype string nullable
• organisation_name string nullable
• organisation_id string nullable
• tender_name string nullable
• tender_id string nullable
• procedure_identifier string nullable
• notice_version_identifier string nullable
• notice_version string nullable
• sdk_version string nullable
• is_evo boolean nullable
• reference_number string nullable
• procurement_name string nullable
• procurement_text string nullable
• contract_type string nullable
• main_cpv_name string nullable
• main_cpv_code string nullable
• procedure_type string nullable
• legal_basis string nullable
• organisations array (default: [])
  • @type string (default: "UvoNoticeOrganisation")
  • name string required
  • reference string nullable
  • ico string nullable
  • dic string nullable
  • website_url string nullable
  • street string nullable
  • building_number string nullable
  • city string nullable
  • postal_code string nullable
  • region string nullable
  • country string nullable
  • email string nullable
  • phone string nullable
  • size string nullable
  • contact_point string nullable
  • is_main_buyer boolean nullable
• fields array (default: [])
  • @type string (default: "UvoNoticeField")
  • section string nullable
  • subsection string nullable
  • group string nullable
  • label string required
  • value 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 notice with this identifier in the ÚVO Bulletin 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.