/cejn/buyers

POST /api/cejn/buyers

Price: 1 credit

Get one Montenegrin contracting authority registered on CeJN by its id: tax number, authority type, activity, street and mailing address, city, e-mail, phone, fax, website and registration status.

How to use it

Pass the id of a cejn/buyers/search row, or the buyer_id of a tender or plan. An id registered only as an economic operator is refused here and opens in cejn/suppliers.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Organisation id (examples: "182")

Response

• @type string (default: "CejnOrganization")
• id string required
• name string nullable
• short_name string nullable
• first_name string nullable
• last_name string nullable
• tax_number string nullable
• registration_number string nullable
• buyer_type string nullable
• organization_form string nullable
• activity_code string nullable
• activity string nullable
• address object nullable
  • @type string (default: "CejnAddress")
  • street string nullable
  • house_number string nullable
  • postcode string nullable
  • city_id string nullable
  • country_id string nullable
• mailing_address object nullable
  • @type string (default: "CejnAddress")
  • street string nullable
  • house_number string nullable
  • postcode string nullable
  • city_id string nullable
  • country_id string nullable
• city string nullable
• country string nullable
• email string nullable
• phone string nullable
• fax string nullable
• website string nullable
• contact_person string nullable
• status string nullable
• version_status string nullable
• is_buyer boolean nullable
• is_supplier boolean nullable
• is_individual boolean nullable
• is_supervisory_institution boolean nullable
• has_applied_as_supplier boolean nullable
• url 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 contracting authority with this id in CeJN 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.