/sicap/direct-acquisitions

POST /api/sicap/direct-acquisitions

Price: 1 credit

Get one SEAP / SICAP direct acquisition by its id or DA code: name and description, state, buyer and supplier with fiscal codes, CPV, estimated and closing value in RON and EUR, publication, decision and finalization dates, rejection reasons, delivery and payment terms, and every catalogue item with its quantity, unit and prices.

How to use it

Pass the id or code of a sicap/direct-acquisitions/search row. buyer_entity_id opens the contracting authority in sicap/buyers.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• direct_acquisition string required — Direct acquisition id or DA code (examples: "123074226", "DA41246056")

Response

• @type string (default: "SicapDirectAcquisition")
• 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
• summary string nullable
• contract_type string nullable
• buyer_entity_id string nullable
• supplier_entity_id string nullable
• closing_value_eur number nullable
• supplier_decided_at integer nullable
• buyer_decided_at integer nullable
• supplier_rejection_reason string nullable
• buyer_rejection_reason string nullable
• delivery_terms string nullable
• payment_terms string nullable
• catalog_items array (default: [])
  • @type string (default: "SicapCatalogItem")
  • id string nullable
  • catalog_item_id string nullable
  • catalog_code string nullable
  • name string nullable
  • item_text string nullable
  • cpv_name string nullable
  • unit string nullable
  • quantity number nullable
  • requested_quantity number nullable
  • catalog_price number nullable
  • estimated_price number nullable
  • estimated_price_eur number nullable
  • closing_price number nullable
  • supplier_email 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 direct acquisition with this identifier in SEAP / SICAP 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.