/mrgovil/tenders/search

POST /api/mrgovil/tenders/search

Price: 20 credits

List Israeli government tenders, exemption notices or central tenders from mr.gov.il, most recently updated first, with the publishing body, publication number, status, procedure number, publication and update dates and the submission deadline of each.

How to use it

Choose kind=tender for open competitive tenders, kind=exemption for notices of intent to contract a named supplier without a tender, kind=central_tender for framework tenders run by the Accountant General. Free text matches the whole publication and is fuzzy; buyer is the portal's own Hebrew name of the publishing body; amount_from and amount_to work on exemptions only. The list carries no amount or supplier — fetch the publication for those.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• kind string required — Publication section to list (one of: "tender", "exemption", "central_tender")
• count integer required — Max number of publications to return (min: 1; max: 500)
• offset integer — How many publications to skip before the first returned one (default: 0; min: 0)
• q string nullable — Free text over the publication (examples: "סימנס"; minLength: 1)
• buyer string nullable — Publishing body, exactly as the portal names it (examples: "משרד החוץ"; minLength: 1)
• category string nullable — Portal subject code (examples: "ZD17", "ZD040002")
• status string nullable — Publication status (one of: "new", "deadline_passed", "published", "updated", "contract_active", "closed", "cancelled", "contract_ended", "upcoming", "being_updated")
• updated_from string nullable — Earliest update date, inclusive (examples: "2026-09-01")
• updated_to string nullable — Latest update date, inclusive (examples: "2026-09-21")
• deadline_from string nullable — Earliest submission deadline, inclusive (examples: "2026-09-22")
• deadline_to string nullable — Latest submission deadline, inclusive (examples: "2026-10-31")
• amount_from number nullable — Minimum contract amount (examples: 1000000; min: 0)
• amount_to number nullable — Maximum contract amount (examples: 50000000; min: 0)
• archive string — Whether archived publications are included (default: "all"; one of: "all", "current", "archived")

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 — amount_from or amount_to was passed for a kind other than exemption, or the portal rejected a category code it does not know 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 — The entity was not found, or a precondition failed 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.