/ezamowienia/notices

POST /api/ezamowienia/notices

Price: 20 credits

Get one e-Zamówienia notice by its id or URL with its full text as numbered sections — buyer, subject, CPV codes, conditions, deadlines and, on result notices, the offers, prices and winners per lot — plus its notice number, type, publication time and procedure id.

How to use it

Pass the id of an ezamowienia/notices/search row. Each section keeps the notice's own numbering and Polish labels, so read prices and winners from the result-notice sections; tender_id resolves in ezamowienia/tenders.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• notice string required — Notice id or notice URL (examples: "08df199c-f6f0-028a-db89-6a00014fc3a1", "https://ezamowienia.gov.pl/mo-client-board/bzp/notice-details/id/08df199c-f6f0-028a-db89-6a00014fc3a1"; minLength: 1)

Response

• @type string (default: "EzamowieniaNotice")
• id string required
• notice_number string nullable
• notice_type string nullable
• notice_type_name string nullable
• published_at integer nullable
• tender_id string nullable
• tender_state string nullable
• form_id string nullable
• sections array (default: [])
  • @type string (default: "EzamowieniaNoticeSection")
  • fields array (default: [])
    • @type string (default: "EzamowieniaNoticeField")
    • number string nullable
    • label string nullable
    • value string 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.