/zakupkikg/buyers

POST /api/zakupkikg/buyers

Price: 1 credit

Buyer (procuring entity) of Kyrgyzstan public procurement from the goszakupki.okmot.kg registry by id: INN, legal form, status, region, legal and actual address, phone and bank details.

How to use it

Takes the `id` of a zakupkikg/buyers/search row or the `buyer.id` of a tender. A supplier id answers 412 here; look it up in zakupkikg/suppliers.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id integer required — Organization id from the registry search (examples: 1667628; min: 1)

Response

• @type string (default: "ZakupkikgCompany")
• 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
• country object nullable
  • @type string (default: "ZakupkikgCountry")
  • id integer nullable
  • iso_code string nullable
  • name string nullable
• region_id integer nullable
• region string nullable
• region_path string nullable
• legal_address string nullable
• actual_address string nullable
• postal_code string nullable
• phone string nullable
• website string nullable
• bank_name string nullable
• bank_bic string nullable
• bank_swift string nullable
• bank_account string nullable
• notes string nullable

Errors

• 422 — The request body did not validate 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 buyer with that id 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.