/zakupkikg/plans

POST /api/zakupkikg/plans

Price: 20 credits

Annual procurement plan of a Kyrgyzstan buyer from goszakupki.okmot.kg by buyer INN and year: status, total, budget lines by account and economic classifier, and the planned items with OKGZ code, quantity, unit, unit price and procurement period.

How to use it

Takes the `inn` and `year` of a zakupkikg/plans/search row. Each budget line lists its planned items in `lines`.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• inn string required — INN of the buyer (examples: "01310199810178")
• year integer required — Plan year (examples: 2026; min: 2000; max: 2100)

Response

• @type string (default: "ZakupkikgPlan")
• inn string required
• year integer required
• buyer_name string nullable
• url string required
• status string nullable
• amount number nullable
• budget_lines array (default: [])
  • @type string (default: "ZakupkikgPlanBudgetLine")
  • id integer nullable
  • status string nullable
  • buyer_name string nullable
  • account string nullable
  • account_title string nullable
  • econ_classifier object nullable
    • @type string (default: "ZakupkikgClassifier")
    • id string nullable
    • name string nullable
    • parent_id string nullable
  • amount number nullable
  • lines array (default: [])
    • @type string (default: "ZakupkikgPlanLine")
    • id integer nullable
    • description string nullable
    • okgz object nullable (see schema ZakupkikgOkgz)
    • quantity number nullable
    • unit string nullable
    • unit_short string nullable
    • unit_price number nullable
    • total number nullable
    • procurement_period string nullable
    • plan_type string nullable
    • account string nullable
    • account_title string nullable
    • econ_classifier object nullable (see schema ZakupkikgClassifier)
    • company_id integer nullable
    • company_name string nullable
    • is_merged boolean nullable

Errors

• 422 — The INN is not 14 digits 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 plan for that buyer and year 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.