/enabavki/plans/search

POST /api/enabavki/plans/search

Price: 5 credits

Search North Macedonia annual public procurement plans on e-nabavki.gov.mk by year. Returns each buyer's plan with its status, version and publication date, newest first.

How to use it

Pass `id` to enabavki/plans for the planned procurements with estimated values, CPV codes and timing.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• year integer nullable — Plan year (examples: 2025; min: 2000; max: 2100)
• offset integer — Rows to skip (default: 0; min: 0)
• count integer required — Max number of annual plans to return (min: 1; max: 2000)

Response

• @type string (default: "EnabavkiPlanSummary")
• id string required
• entity_id string nullable
• year integer nullable
• buyer_name string nullable
• status string nullable
• status_type_id string nullable
• plan_stage string nullable
• current_version integer nullable
• created_date string nullable
• published_date string nullable
• has_items boolean nullable
• is_editable_after_publication boolean nullable
• has_version_request boolean nullable

Errors

• 422 — The year is outside 2000-2100 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.