/sicap/direct-acquisitions/search

POST /api/sicap/direct-acquisitions/search

Price: 20 credits

Search Romania's SEAP / SICAP direct acquisitions — low-value purchases from the electronic catalogue — by state, name, contracting authority fiscal code, publication date and finalization date, with the buyer, supplier, CPV, estimated and closing value and the decision deadlines of each acquisition.

How to use it

Without status the search covers finished acquisitions; status offering lists the ones still open for the supplier and is the one that takes published_from and published_to. Pass the id of a row to sicap/direct-acquisitions for the catalogue items, prices and quantities.

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: 1000)
• status string nullable — State of the direct acquisition (one of: "offering", "offer_accepted", "conditions_refused", "offer_refused", "conditions_not_accepted_in_time", "offer_not_accepted_in_time")
• keyword string nullable — Words in the direct acquisition name (examples: "hartie"; minLength: 2)
• buyer_fiscal_code string nullable — Contracting authority fiscal code (CUI) (examples: "4323209")
• published_from string nullable — Earliest publication date, inclusive (examples: "2026-09-20")
• published_to string nullable — Latest publication date, inclusive (examples: "2026-09-23")
• finalized_from string nullable — Earliest finalization date, inclusive (examples: "2026-09-20")
• finalized_to string nullable — Latest finalization date, inclusive (examples: "2026-09-23")

Response

• @type string (default: "SicapDirectAcquisitionSummary")
• id string required
• code string nullable
• name string nullable
• status string nullable
• cpv object nullable
  • @type string (default: "SicapCpv")
  • code string nullable
  • name string nullable
• buyer object nullable
  • @type string (default: "SicapParty")
  • name string required
  • fiscal_code string nullable
• supplier object nullable
  • @type string (default: "SicapParty")
  • name string required
  • fiscal_code string nullable
• estimated_value_ron number nullable
• estimated_value_eur number nullable
• closing_value_ron number nullable
• published_at integer nullable
• finalized_at integer nullable
• supplier_deadline_at integer nullable
• buyer_deadline_at integer 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.