/enabavki/awards/search

POST /api/enabavki/awards/search

Price: 10 credits

Search North Macedonia public procurement award decisions on e-nabavki.gov.mk by subject, procedure number, procedure and decision date. Returns the decision with buyer, winner, bid count, lot and the decision text, newest first.

How to use it

Covers decisions from 2023 on. A divided tender has one row per lot with `lot_id`; `call_for_tender_id` equals the `call_for_tender_id` of the enabavki/tenders dossier.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• subject string nullable — Words in the subject (examples: "гориво"; minLength: 1)
• process_number string nullable — Procedure number (examples: "15622/2026"; minLength: 1)
• procedure_type string nullable — Procurement procedure (one of: "open", "restricted", "negotiated_with_notice", "competitive_dialogue", "request_for_proposal", "design_contest", "negotiated_without_notice", "qualification_system", "low_value", "simplified_open", "competitive_negotiation", "innovation_partnership", "special_services")
• date_from string nullable — Decided on or after (format: date; examples: "2026-09-01")
• date_to string nullable — Decided on or before (format: date; examples: "2026-09-10")
• offset integer — Rows to skip (default: 0; min: 0)
• count integer required — Max number of award decisions to return (min: 1; max: 2000)

Response

• @type string (default: "EnabavkiAward")
• id string required
• call_for_tender_id string nullable
• lot_id string nullable
• process_number string nullable
• buyer_name string nullable
• subject string nullable
• procedure_type string nullable
• procedure_type_id string nullable
• decided_at integer nullable
• decision_text string nullable
• winner_name string nullable
• bid_count integer nullable
• stage_number integer nullable
• offer_type_id string nullable
• framework_type string nullable
• auction_type string nullable
• auction_round_id string nullable
• min_auction_price number nullable
• is_divided boolean nullable
• is_price_only boolean nullable
• is_auction boolean nullable
• is_direct_auction boolean nullable
• is_reevaluated boolean nullable
• has_lot_been_reevaluated boolean nullable
• is_small_procurement boolean nullable
• uses_electronic_tools boolean nullable
• is_complained boolean nullable

Errors

• 422 — A date is not YYYY-MM-DD, a range is inverted, or the portal rejected the filter values 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.