/cejn/plans/search

POST /api/cejn/plans/search

Price: 10 credits

Search the annual public procurement plans Montenegrin contracting authorities publish on CeJN by plan name, contracting authority name, id or tax number, plan year, plan item description, subject and procedure type and total value, with the owner, year, responsible person and approval state of each plan.

How to use it

Pass a row id to cejn/plans for the plan's items with CPV codes, values and planned procedures; buyer_id opens the contracting authority in cejn/buyers.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• offset integer — Number of matching results to skip (default: 0; examples: 0, 5000; min: 0; max: 1000000)
• count integer required — Max number of results (min: 1; max: 3000)
• buyer_name string nullable — Part of the contracting authority name (examples: "OPŠTINA")
• buyer_id string nullable — Contracting authority id (examples: "182")
• buyer_tax_number string nullable — Contracting authority tax number (PIB) (examples: "02816296")
• plan_year integer nullable — Plan year (examples: 2026; min: 2000; max: 2100)
• item_description string nullable — Part of a plan item description (examples: "gorivo")
• item_subject_type string nullable — Subject type of a plan item (one of: "goods", "services", "works")
• item_procedure_type string nullable — Procedure type of a plan item (one of: "small_procurement", "open", "restricted", "competitive_with_negotiation", "negotiation_without_publication", "innovation_partnership", "competitive_dialogue", "negotiation_with_publication", "framework_mini_call_off")
• value_min number nullable — Minimum plan value in EUR (examples: 1000000; min: 0)
• value_max number nullable — Maximum plan value in EUR (examples: 1000; min: 0)

Response

• @type string (default: "CejnPlanSummary")
• id string required
• name string nullable
• plan_year integer nullable
• buyer_name string nullable
• buyer_id string nullable
• responsible_person string nullable
• contact_person string nullable
• status string nullable
• status_name string nullable
• is_approved boolean nullable
• is_awaiting_approval boolean nullable
• approved_at integer nullable
• created_at integer 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 — 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.