/mrgovil/tenders

POST /api/mrgovil/tenders

Price: 5 credits

Get one mr.gov.il publication by its publication number: a tender with its publishing body, status, procedure number, submission window, contact, subjects and attachments, or an exemption notice adding the nature and reasons of the engagement, the supplier and its company number, the amount, currency, contract period and the regulation it relies on.

How to use it

Use the publication number from a search result or from a /p/<number> portal URL. Exemption notices are where the supplier, amount and contract dates live; tenders carry the submission window and attachments. Records go back to 2005 and old ones may have empty publisher, contact and dates.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• number string required — Publication number or publication URL (examples: "4000621291", "644938", "https://mr.gov.il/ilgstorefront/he/p/6180")

Response

• @type string (default: "MrgovilTender")
• id string required
• notice_type string nullable
• description string nullable
• reasons string nullable
• status string nullable
• stage string required
• procedure_number string nullable
• regulation string nullable
• buyer object nullable
  • @type string (default: "MrgovilParty")
  • name string nullable
  • company_number string nullable
• suppliers array (default: [])
  • @type string (default: "MrgovilParty")
  • name string nullable
  • company_number string nullable
• value object nullable
  • @type string (default: "MrgovilValue")
  • amount number nullable
  • currency string nullable
• dates object nullable
  • @type string (default: "MrgovilDates")
  • published_at integer nullable
  • updated_at integer nullable
  • submission_start_at integer nullable
  • deadline_at integer nullable
  • contract_start_at integer nullable
  • contract_end_at integer nullable
• subjects array (default: [])
• contact object nullable
  • @type string (default: "MrgovilContact")
  • name string nullable
  • email string nullable
• attachments array (default: [])
  • @type string (default: "MrgovilAttachment")
  • id string required
  • description string nullable
  • url string required
  • uploaded_at integer nullable
• country string (default: "IL")
• 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 publication carries this number 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.