/enarocanje/tenders/search

POST /api/enarocanje/tenders/search

Price: 20 credits

Search Slovenia's e-JN procurement notices — contract notices, award notices, prior information, corrections and contract modifications, current and legacy forms — by title, buyer name or registration number, procedure or notice number, lot title, contract type, phase, CPV, publication date and submission deadline, newest first, with the buyer, form type, phase and publication time of each notice.

How to use it

Each row is one published notice, so a procedure appears once per notice it published; procedure_id and notice_number group them. Text filters match the start of the title or buyer name, case-insensitively. Pass a row id to enarocanje/tenders for the full notice with lots, winners and contracts.

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)
• published_from string nullable — Earliest publication date, inclusive (examples: "2026-09-01")
• published_to string nullable — Latest publication date, inclusive (examples: "2026-09-10")
• count integer required — Max number of results (min: 1; max: 5000)
• buyer_name string nullable — Start of the contracting authority name (examples: "OBČINA")
• buyer_registration_number string nullable — Contracting authority registration number (examples: "5874483000")
• notice_number string nullable — Procedure or notice number (examples: "JN006336/2026")
• lot_title string nullable — Start of a lot title (examples: "Sklop")
• contract_type string nullable — Type of contract (one of: "services", "supplies", "works")
• phases array nullable — Procedure phases to include (one of: "planning", "competition", "prior_transparency", "result", "contract_modification"; minItems: 1)
• cpv array nullable — CPV codes, including their subordinate codes (examples: ["45233140"]; minItems: 1)
• deadline_from string nullable — Earliest tender submission deadline, inclusive (examples: "2026-09-25")
• deadline_to string nullable — Latest tender submission deadline, inclusive (examples: "2026-10-31")

Response

• @type string (default: "EnarocanjeTenderSummary")
• id string required
• procedure_id string nullable
• notice_number string nullable
• buyer_name string nullable
• buyer_registration_number string nullable
• form_code string nullable
• form_label string nullable
• phase string nullable
• published_at integer nullable
• is_new_form boolean nullable
• is_eu_published boolean nullable
• is_electronic_submission_required boolean nullable
• is_dynamic_purchasing_system boolean nullable
• is_framework_agreement boolean nullable
• legacy_id 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 — 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.