/zakupkikg/tenders/search

POST /api/zakupkikg/tenders/search

Price: 5 credits

Search Kyrgyzstan public procurement tenders on goszakupki.okmot.kg by name words, status, procurement method, buyer, OKGZ classifier code, planned amount and publication date. Returns the tender with buyer, method, amount, bid deadline and lots.

How to use it

Rows with an empty `published_at` (statuses NEW, PENDING_COMMISSION and REJECTED) have no public page and answer 412 in zakupkikg/tenders. Cancelled tenders are listed separately in zakupkikg/tenders/cancelled. Pass `id` to zakupkikg/tenders for lots with items, bids, evaluation and contracts.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Words of the tender or lot name (examples: "бумага", "ГСМ"; minLength: 2)
• status string nullable — Tender status (one of: "NEW", "PENDING_COMMISSION", "REJECTED", "VERIFIED_PUBLISHED", "PROTOCOL_OPENED", "PROTOCOL_OF_PROCEDURE", "EVALUATION_FIRST_PACKAGE_PUBLISHED", "EVALUATION_THIRD_STAGE_COMPLETED", "EVALUATION_COMPLATED", "WAITING_SIGN_CONTRACT", "CONTRACT_SIGNED", "FRAMEWORK_CONTRACT_SIGNED", "REJECTED_BY_INCOMPLETE")
• method string nullable — Procurement method (one of: "REQUEST_FOR_QUOTATION", "REQUEST_FOR_QUOTATION_FRAMEWORK_AGREEMENT", "TWO_PACKAGE_UNLIMITED", "CONSULTATION_ONE_STAGE", "NEGOTIATION_UNLIMITED")
• buyer_id integer nullable — Buyer id, as in zakupkikg/buyers/search (examples: 878175; min: 1)
• okgz_code string nullable — OKGZ classifier code or its leading digits (examples: "09136", "091")
• min_amount number nullable — Lowest planned amount, KGS (examples: 100000; min: 0)
• max_amount number nullable — Highest planned amount, KGS (examples: 200000; min: 0)
• published_from string nullable — Published on or after (examples: "2026-09-01")
• published_to string nullable — Published on or before (examples: "2026-09-30")
• offset integer — Rows to skip (default: 0; min: 0)
• count integer required — Max number of tenders to return (min: 1; max: 1000)

Response

• @type string (default: "ZakupkikgTenderSummary")
• id string required
• number string nullable
• name string nullable
• url string required
• status string nullable
• method string nullable
• procurement_type string nullable
• buyer object nullable
  • @type string (default: "ZakupkikgCompanyRef")
  • id integer nullable
  • inn string nullable
  • name string nullable
• total number nullable
• region string nullable
• created_at integer nullable
• published_at integer nullable
• bid_deadline_at integer nullable
• lots array (default: [])
  • @type string (default: "ZakupkikgLotRef")
  • id string nullable
  • number string nullable
  • name string nullable

Errors

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