/enarocanje/contracts

POST /api/enarocanje/contracts

Price: 5 credits

Get one contract or contract amendment published on e-JN by its id: value, signing date and duration, CPV, contract kind and type, contracting authorities and suppliers with registration numbers and addresses, contract documents with download links, recorded payments, and the related base contract or amendments.

How to use it

Pass the id of an enarocanje/contracts/search row. tender_id opens the notice the contract was reported on in enarocanje/tenders; related_contracts holds the amendments of a contract, or the base contract of an amendment.

Parameters

• access-token string required

Request body

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

Response

• @type string (default: "EnarocanjeContract")
• id string required
• name string nullable
• tender_name string nullable
• kind string nullable
• contract_category string nullable
• contract_type string nullable
• cpv object nullable
  • @type string (default: "EnarocanjeCpv")
  • code string nullable
  • name string nullable
• value number nullable
• signed_date string nullable
• start_date string nullable
• end_date string nullable
• duration_months integer nullable
• internal_number string nullable
• reference_number string nullable
• notice_number string nullable
• previous_notice_number string nullable
• procedure_number string nullable
• tender_id string nullable
• procedure_id string nullable
• base_contract_id string nullable
• form_code string nullable
• form_name string nullable
• status string nullable
• is_framework_agreement boolean nullable
• buyers array (default: [])
  • @type string (default: "EnarocanjeOrganization")
  • name string nullable
  • registration_number string nullable
  • address string nullable
  • postcode string nullable
  • city string nullable
  • country string nullable
  • nuts object nullable
    • @type string (default: "EnarocanjeNuts")
    • code string nullable
    • name string nullable
  • email string nullable
  • website string nullable
  • phone string nullable
  • buyer_type_id string nullable
  • activity_id string nullable
  • is_central_purchasing_body boolean nullable
  • size_id string nullable
  • is_listed boolean nullable
• suppliers array (default: [])
  • @type string (default: "EnarocanjeOrganization")
  • name string nullable
  • registration_number string nullable
  • address string nullable
  • postcode string nullable
  • city string nullable
  • country string nullable
  • nuts object nullable
    • @type string (default: "EnarocanjeNuts")
    • code string nullable
    • name string nullable
  • email string nullable
  • website string nullable
  • phone string nullable
  • buyer_type_id string nullable
  • activity_id string nullable
  • is_central_purchasing_body boolean nullable
  • size_id string nullable
  • is_listed boolean nullable
• documents array (default: [])
  • @type string (default: "EnarocanjeDocument")
  • id string nullable
  • name string nullable
  • url string nullable
  • type_id string nullable
  • uploaded_at integer nullable
• payments array (default: [])
  • @type string (default: "EnarocanjePayment")
  • payee_name string nullable
  • payee_tax_number string nullable
  • paid_date string nullable
  • amount number nullable
  • currency string nullable
• related_contracts array (default: [])
• published_at integer nullable
• updated_at integer nullable
• notice_updated_at integer 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 — No contract with this id on the e-JN portal 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.