/cejn/tenders/contracts

POST /api/cejn/tenders/contracts

Price: 5 credits

List the contracts concluded under one CeJN tender: supplier names and id, contract value and VAT, conclusion, execution and termination dates, the phase and proposal each contract came from, the id of the framework agreement a call-off contract is based on, whether it covers the whole tender, and its status.

How to use it

Pass a cejn/tenders/search row id. A tender that is still open or was cancelled usually has no contracts yet, and the call then returns an empty list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• tender string required — Tender id (examples: "40000")

Response

• @type string (default: "CejnContract")
• id string required
• tender_id string nullable
• kind string nullable
• suppliers string nullable
• supplier_id string nullable
• value object nullable
  • @type string (default: "CejnMoney")
  • amount number nullable
  • currency string nullable
• vat object nullable
  • @type string (default: "CejnMoney")
  • amount number nullable
  • currency string nullable
• concluded_date string nullable
• amended_concluded_date string nullable
• execution_date string nullable
• termination_date string nullable
• amendment_description string nullable
• status string nullable
• phase_id string nullable
• phase_description string nullable
• phase_type_id string nullable
• proposal_id string nullable
• framework_agreement_id string nullable
• is_whole_tender boolean nullable
• is_framework_agreement_tender boolean 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 — No tender with this id in CeJN 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.