/goszakup/blacklist/search

POST /api/goszakup/blacklist/search

Price: 5 credits

Search the Kazakhstan register of unreliable public procurement suppliers on zakup.gov.kz by supplier name words, BIN/IIN, date of entry, filing system and register (state or quasi-public sector). Returns the entry with the supplier, its directors and founders.

How to use it

The row names the supplier only; pass `id` to goszakup/blacklist for the reason, the court decision, the tender and contract behind the entry and the planned exclusion date.

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 supplier name (examples: "ТОО", "Аэропорт"; minLength: 2)
• supplier_bin string nullable — BIN or IIN of the supplier (examples: "991040000402")
• included_from string nullable — Entered the register on or after (examples: "2026-01-01")
• system string nullable — Procurement system that filed the entry (one of: "egz", "mitwork", "skk", "epz")
• quasi_public boolean nullable — true: only the quasi-public sector register; false: only the state procurement register. Left empty, a search by supplier_bin covers both registers and every other search the state register
• offset integer — Rows to skip (default: 0; min: 0; max: 9999)
• count integer required — Max number of register entries to return (min: 1; max: 1000)

Response

• @type string (default: "GoszakupBlacklistSummary")
• id integer required
• external_id integer nullable
• system object nullable
  • @type string (default: "GoszakupRef")
  • id integer nullable
  • name string nullable
  • name_kk string nullable
• supplier object nullable
  • @type string (default: "GoszakupBlacklistedSupplier")
  • id integer nullable
  • iin_bin string nullable
  • name string nullable
  • name_kk string nullable
  • directors array (default: [])
    • @type string (default: "GoszakupPerson")
    • id integer nullable
    • full_name string nullable
    • iin string nullable
    • rnn string nullable
  • founders array (default: [])
    • @type string (default: "GoszakupPerson")
    • id integer nullable
    • full_name string nullable
    • iin string nullable
    • rnn string nullable

Errors

• 422 — The BIN is not 12 digits or a date is not YYYY-MM-DD 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.