/enabavki/plans

POST /api/enabavki/plans

Price: 20 credits

North Macedonia annual public procurement plan from e-nabavki.gov.mk by id: the buyer with contacts, plan versions, and every planned procurement with subject, contract type, procedure, estimated value, expected start and CPV codes, in the plan's current version. On the largest plans (over 1,000 planned procurements) the list can come back short: `item_count` still gives the plan's full count and an X-Warning header states how many were returned.

How to use it

Takes the `id` of an enabavki/plans/search row; `planned_procurements` are the planned procurements of the current version.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Annual plan id from enabavki/plans/search (examples: "3d55ce7d-e2e5-4334-9fa9-b3d9012ad456"; pattern: ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$)

Response

• @type string (default: "EnabavkiPlan")
• id string required
• entity_id string nullable
• year integer nullable
• buyer_name string nullable
• buyer object nullable
  • @type string (default: "EnabavkiBuyer")
  • name string nullable
  • address string nullable
  • city string nullable
  • postal_code string nullable
  • category string nullable
  • main_activity string nullable
  • email string nullable
  • phone string nullable
  • website string nullable
  • contact_person string nullable
  • contact_phone string nullable
  • contact_email string nullable
  • contact_fax string nullable
  • contact_page string nullable
  • authorized_person string nullable
  • authorized_person_email string nullable
  • authorized_person_phone 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
• covers_all_procurements boolean nullable
• is_editable_after_publication boolean nullable
• has_version_request boolean nullable
• versions array (default: [])
  • @type string (default: "EnabavkiPlanVersion")
  • number integer nullable
  • name string nullable
  • published_at integer nullable
• item_count integer nullable
• planned_procurements array (default: [])
  • @type string (default: "EnabavkiPlanItem")
  • id string nullable
  • subject string nullable
  • contract_type string nullable
  • contract_type_id string nullable
  • procedure_type string nullable
  • procedure_type_id string nullable
  • estimated_value number nullable
  • expected_start_at integer nullable
  • expected_month integer nullable
  • note string nullable
  • cpvs array (default: [])
    • @type string (default: "EnabavkiPlanCpv")
    • code string nullable
    • description string nullable
    • code_id string nullable
    • code_type string nullable
    • nomenclature_type string nullable
  • procedures array (default: [])
    • @type string (default: "EnabavkiPlanProcedure")
    • id string nullable
    • procedure_type_id string nullable
  • record_type_id string nullable
  • plan_stage string nullable
  • can_be_announced integer nullable
  • published_at integer nullable
  • created_at integer nullable
  • initial_version_id string nullable
  • has_previous_version boolean nullable
  • is_central_institution boolean nullable
  • is_from_spreadsheet boolean nullable
  • is_on_emarket boolean nullable

Errors

• 422 — The id is not a GUID 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 annual plan with that id 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.