/zakupkikg/direct_contracts/search

POST /api/zakupkikg/direct_contracts/search

Price: 5 credits

Search single-source (direct) public procurement contracts of Kyrgyzstan on goszakupki.okmot.kg by contract number, buyer name, supplier INN or name and publication date. Returns the contract with its buyer, supplier and dates.

How to use it

Pass `id` to zakupkikg/direct_contracts for the items with prices, the legal ground for the single source, payments and delivery schedule. Contracts from competitive tenders are in zakupkikg/contracts/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• contract_number string nullable — Contract number given by the buyer (examples: "59"; minLength: 1)
• buyer_name string nullable — Words of the buyer name (examples: "Центр семейной медицины"; minLength: 2)
• supplier_inn string nullable — Supplier INN (examples: "02701200010106")
• supplier_name string nullable — Words of the supplier name (examples: "Medco"; minLength: 2)
• published_from string nullable — Published on or after (examples: "2026-09-20")
• published_to string nullable — Published on or before (examples: "2026-09-25")
• offset integer — Rows to skip (default: 0; min: 0)
• count integer required — Max number of contracts to return (min: 1; max: 1000)

Response

• @type string (default: "ZakupkikgDirectContractSummary")
• id string required
• number string nullable
• system_number string nullable
• sequence integer nullable
• url string required
• contract_type string nullable
• buyer_name string nullable
• supplier_inn string nullable
• supplier_name string nullable
• contract_date string nullable
• published_date string nullable

Errors

• 422 — A date is not YYYY-MM-DD, one publication date lacks its pair, or 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 — 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.