/enarocanje/reviews/search

POST /api/enarocanje/reviews/search

Price: 20 credits

Search the requests for legal protection (eRevizija) filed against Slovenian procurement procedures by subject, contracting authority name or registration number, procedure number and procedure state, newest first, with the applicant, the challenged act, the state and the filing time of each request.

How to use it

tender_id opens the challenged notice in enarocanje/tenders. Text filters match the start of the subject or buyer name, case-insensitively.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• offset integer — Number of matching results to skip (default: 0; examples: 0, 5000; min: 0; max: 1000000)
• count integer required — Max number of results (min: 1; max: 1500)
• subject string nullable — Start of the procurement subject (examples: "Dobava")
• buyer_name string nullable — Start of the contracting authority name (examples: "Univerzitetni")
• buyer_registration_number string nullable — Contracting authority registration number (examples: "5053919000")
• notice_number string nullable — Procedure number (examples: "JN003273/2026")
• status string nullable — State of the review procedure (one of: "pre_review", "appeal", "review", "closed", "other")

Response

• @type string (default: "EnarocanjeReview")
• id string required
• tender_id string nullable
• procedure_number string nullable
• subject string nullable
• applicant_name string nullable
• applicant_registration_number string nullable
• buyer_name string nullable
• buyer_registration_number string nullable
• status string nullable
• status_id string nullable
• challenged_act string nullable
• challenged_act_id string nullable
• submitted_at integer nullable
• tender_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.