/eopbg/buyers

POST /api/eopbg/buyers

Price: 2 credits

Get one Bulgarian contracting authority from EOP by its id: name, EIK/BULSTAT, register number, address, website, phone, logo, the contact person with email and phone, and its counts of tenders, contracts and published notices.

How to use it

Pass the id of an eopbg/buyers/search row or the buyer id of a tender. Use registry_number with eopbg/tenders/search or eopbg/contracts/search to list the authority's procedures and contracts.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• buyer string required — Contracting authority id (examples: "1113"; minLength: 1)

Response

• @type string (default: "EopbgBuyerProfile")
• id string required
• guid string nullable
• name string required
• registry_number string nullable
• batch_number string nullable
• city string nullable
• tenders_count integer nullable
• contracts_count integer nullable
• notices_count integer nullable
• preliminary_notices_count integer nullable
• country string (default: "BG")
• website string nullable
• phone string nullable
• image string nullable
• address object nullable
  • @type string (default: "EopbgAddress")
  • street string nullable
  • city string nullable
  • postcode string nullable
• contact object nullable
  • @type string (default: "EopbgContact")
  • name string nullable
  • email string nullable
  • phone 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 record with this identifier on EOP 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.