/ezamowienia/tenders

POST /api/ezamowienia/tenders

Price: 10 credits

Get one procurement procedure run on e-Zamówienia by its OCDS id or URL: title, reference number, procedure type, state and stage, buyer, lots with their budgets, submission terms, the BZP and TED notice numbers and the procedure documents with their download links.

How to use it

Pass the tender_id of an ezamowienia/notices/search row. A procedure run outside the platform answers 412, and winners and prices live in the result notice, which ezamowienia/notices returns.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• tender string required — Procedure id or procedure URL (examples: "ocds-148610-7937d65e-6741-4eff-acf9-5027f9b5d222", "https://ezamowienia.gov.pl/mp-client/search/list/ocds-148610-29fd0155-3989-4be7-97ae-8b2e3320ec02"; minLength: 1)

Response

• @type string (default: "EzamowieniaTender")
• id string required
• reference_number string nullable
• tender_type string nullable
• concession_type string nullable
• notice_concerns string nullable
• competition_type string nullable
• competition_kind string nullable
• state string nullable
• stage string nullable
• stage_reason string nullable
• bzp_number string nullable
• notice_number string nullable
• result_notice_number string nullable
• ted_contract_notice_number string nullable
• contract_award_notice_numbers array (default: [])
• is_below_eu_threshold boolean nullable
• is_partial boolean nullable
• lots_count integer nullable
• amount number nullable
• currency string nullable
• is_amount_published boolean nullable
• additional_information string nullable
• buyer object nullable
  • @type string (default: "EzamowieniaTenderBuyer")
  • id string nullable
  • name string nullable
  • part_name string nullable
  • city string nullable
  • province string nullable
• tender_plan_organization_id string nullable
• tender_plan_item_ids array (default: [])
• terms array (default: [])
  • @type string (default: "EzamowieniaTerm")
  • kind string nullable
  • date_at integer nullable
  • is_valid boolean nullable
• lots array (default: [])
  • @type string (default: "EzamowieniaLot")
  • id string nullable
  • number integer nullable
  • stage string nullable
  • additional_information string nullable
  • amount number nullable
  • currency string nullable
• phases array (default: [])
• competition_aliases array (default: [])
• documents array (default: [])
  • @type string (default: "EzamowieniaDocument")
  • id string nullable
  • name string nullable
  • file_name string nullable
  • state string nullable
  • url string nullable
  • created_at integer nullable
  • published_at integer nullable
  • deleted_at integer nullable
  • delete_reason string nullable
• created_at integer nullable
• initiated_at integer nullable
• cancellation_at integer nullable
• submission_at integer nullable
• opening_at integer nullable
• is_public boolean nullable
• is_proceeding_on_platform boolean nullable
• has_published_notice boolean nullable
• is_position_removed boolean nullable
• country string (default: "PL")
• url string required

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 e-Zamowienia 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.