/enarocanje/awards

POST /api/enarocanje/awards

Price: 1 credit

Get one e-JN award decision by its id: the procurement title and reference number, the contracting authority with its registration number and address, the decision document with its download link, and the publication time.

How to use it

Pass the id of an enarocanje/awards/search row; decision ids and notice ids are separate numbering schemes, so a notice id does not identify a decision. procedure_number, passed as notice_number to enarocanje/tenders/search, finds the procedure's notices.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• award string required — Award decision id (examples: "330635")

Response

• @type string (default: "EnarocanjeAward")
• id string required
• notice_number string nullable
• procedure_number string nullable
• reference_number string nullable
• form_name string nullable
• buyer object nullable
  • @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
• decision_document_name string nullable
• decision_document_url string nullable
• published_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 award decision 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.