/sicap/tenders/search

POST /api/sicap/tenders/search

Price: 20 credits

Search Romania's SEAP / SICAP procurement notices — contract notices, simplified notices, requests for quotation, concession, design-contest and dynamic-system invitations — by name, notice number, CPV, contracting authority fiscal code, notice type, procedure state and type, contract type, award criterion, estimated value in RON, publication date and submission deadline, with the buyer, CPV, estimated value, procedure state and submission deadline of each notice.

How to use it

Filters combine with AND; a search matching more than 3000 notices returns 3000 of them, so narrow it with published_from and published_to. Pass the id or notice_number of a row to sicap/tenders for the full notice with lots, conditions and award criteria.

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: 3000)
• keyword string nullable — Words in the procurement name (examples: "paza"; minLength: 2)
• buyer_fiscal_code string nullable — Contracting authority fiscal code (CUI) (examples: "4323209")
• contract_type string nullable — Type of contract (one of: "supplies", "services", "works")
• published_from string nullable — Earliest publication date, inclusive (examples: "2026-08-24")
• published_to string nullable — Latest publication date, inclusive (examples: "2026-09-23")
• notice_number string nullable — Notice number (examples: "CN1084731", "SCN1125565", "RFQ1000538")
• notice_types array nullable — Notice types to include (one of: "contract_notice", "simplified_notice", "request_for_quotation", "concession_notice", "design_contest_notice", "dynamic_system_invitation"; minItems: 1)
• cpv string nullable — CPV code or its leading digits (examples: "79713000-5", "79713")
• procedure_state string nullable — State of the procedure (one of: "ongoing", "cancelled", "suspended", "awarded")
• procedure_type string nullable — Procurement procedure (one of: "open", "restricted", "restricted_accelerated", "negotiated", "negotiated_accelerated", "competitive_dialogue", "negotiated_without_publication", "direct_purchase", "request_for_quotation", "open_design_contest", "restricted_design_contest", "open_accelerated", "innovation_partnership", "own_simplified_procedure", "own_rules_annex_2", "competitive_with_negotiation", "competitive_with_negotiation_accelerated", "simplified")
• award_criterion string nullable — Award criterion (one of: "lowest_price", "best_price_quality", "lowest_cost", "best_cost_quality")
• value_min number nullable — Minimum estimated value in RON (examples: 1000000; min: 0)
• value_max number nullable — Maximum estimated value in RON (examples: 10000; min: 0)
• deadline_from string nullable — Earliest tender submission deadline, inclusive (examples: "2026-10-01")
• deadline_to string nullable — Latest tender submission deadline, inclusive (examples: "2026-10-31")

Response

• @type string (default: "SicapTenderSummary")
• id string required
• seap_id string nullable
• notice_id string nullable
• procedure_id string nullable
• notice_number string nullable
• notice_type string nullable
• notice_state string nullable
• procedure_state string nullable
• name string nullable
• buyer object nullable
  • @type string (default: "SicapParty")
  • name string required
  • fiscal_code string nullable
• contract_type string nullable
• procedure_type string nullable
• assignment_type string nullable
• cpv object nullable
  • @type string (default: "SicapCpv")
  • code string nullable
  • name string nullable
• estimated_value_ron number nullable
• state_changed_at integer nullable
• deadline_at integer nullable
• earliest_deadline_at integer nullable
• errata_count integer nullable
• is_online boolean nullable
• has_lots boolean nullable
• has_appeal 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.