/zakupkikg/buyers/search

POST /api/zakupkikg/buyers/search

Price: 5 credits

Search the registry of Kyrgyzstan public procurement buyers (procuring entities) on goszakupki.okmot.kg by name words, INN and registration status. Returns the buyer with legal form, status and registration date. A registry row that cannot be read is left out in place and named in the X-Warning header.

How to use it

The row `id` is the `buyer_id` of zakupkikg/tenders/search and the key of zakupkikg/buyers for address, phone and bank details. An organization that also supplies has a separate id in zakupkikg/suppliers.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• name string nullable — Words of the organization name (examples: "Айыл"; minLength: 2)
• inn string nullable — INN of the organization (examples: "01405202410214")
• status string nullable — Registration status on the portal (one of: "ACTIVE", "INACTIVE")
• offset integer — Rows to skip (default: 0; min: 0)
• count integer required — Max number of organizations to return (min: 1; max: 1000)

Response

• @type string (default: "ZakupkikgCompanySummary")
• id integer required
• inn string nullable
• name string nullable
• url string required
• legal_form string nullable
• status string nullable
• company_type string nullable
• form object nullable
  • @type string (default: "ZakupkikgCompanyForm")
  • id integer nullable
  • form_type string nullable
  • role_name string nullable
  • role_description string nullable
• registered_date string 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 — 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.