/riigihanked/tenders/search

POST /api/riigihanked/tenders/search

Price: 20 credits

Search the Estonian public procurement register — every procurement of Estonian contracting authorities since 2006, simple and national-threshold procurements included — by name, reference number, state, contract type, procedure, sector, buyer name or registry code, tenderer name or registry code, CPV, contract value range and publication date, with the buyer, main CPV, publication and submission dates and the notice, contract and dispute counts of each procurement. Newest publications first.

How to use it

Filters combine with AND; value_min and value_max apply to contract value, and supplier_registry_code takes a contractor's registry code as riigihanked/tenders shows it. Pass the id of a row to riigihanked/tenders for parts, notices and contracts with contractors.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of results (min: 1; max: 2000)
• keyword string nullable — Words in the procurement name (examples: "ravim"; minLength: 1)
• reference_number string nullable — Procurement reference number (examples: "315814")
• status string nullable — Procurement state (one of: "preparation", "prior_information_published", "pending_a_prior_information_notice", "prior_information_notice", "started", "evaluation", "contract_performance", "open_for_entry", "closed_for_entry", "prior_notice_is_progress", "contract_completed", "requests_to_participate_submitted", "pending_a_solution", "pending_a_tender", "pending_a_contract", "terminated", "cancelled")
• contract_type string nullable — Type of contract (one of: "supplies", "public_works", "special_services", "social_services", "services")
• procedure_type string nullable — Procurement procedure (one of: "open_procedure", "dynamic_procurement_system_s_simple_procurement_invalid", "dynamic_procurement_system_s_restricted_procedure", "public_works_concession_until_18_10_2018", "competitive_procedure_with_negotiation", "negotiated_procedure_with_prior_publication_and_reduced_time_limits_until_18_10_2018", "competitive_procedure_with_negotiation_gq", "open_design_contest", "innovation_partnership", "concession_contract", "based_on_an_exception", "simple_procurement", "simple_procurement_lm", "simple_procurement_lq", "light_regime_for_buying_services", "reopening_of_competition_on_the_basis_of_framework_contract", "other_acquisition", "restricted_procedure", "restricted_procedure_pd", "prior_notice_for_procurement_start", "design_contest_with_limited_number_of_participants", "restricted_procedure_with_reduced_time_limit_until_18_10_2018", "prior_information_notice_for_shortening_deadlines", "restricted_procedure_pq", "qualification_system", "special_procedure_of_social_and_special_services", "procurement_related_to_the_advance_notice_of_social_and_special_services", "negotiated_procedure_without_prior_publication_of_tender_notice", "negotiated_procedure_without_prior_publication_of_tender_notice_tq", "market_consultations", "competitive_dialogue", "low_value_purchase")
• sector string nullable — Procurement sector (one of: "defence_and_security", "public_sector", "utilities")
• buyer_name string nullable — Words in the contracting authority name (examples: "Tallinna"; minLength: 1)
• buyer_registry_code string nullable — Contracting authority registry code (examples: "90001478")
• supplier_name string nullable — Words in a tenderer or contractor name (examples: "Kavepro"; minLength: 1)
• supplier_registry_code string nullable — Tenderer or contractor registry code (examples: "16314158")
• cpv string nullable — CPV code with check digit (examples: "33600000-6")
• value_min number nullable — Minimum contract value in EUR (examples: 100000; min: 0)
• value_max number nullable — Maximum contract value in EUR (examples: 1000; min: 0)
• published_from string nullable — Earliest publication date, inclusive (examples: "2026-08-24")
• published_to string nullable — Latest publication date, inclusive (examples: "2026-09-23")

Response

• @type string (default: "RiigihankedTenderSummary")
• id string required
• reference_number string nullable
• description string nullable
• status string nullable
• stage string nullable
• contract_type string nullable
• procedure_type string nullable
• buyer object nullable
  • @type string (default: "RiigihankedOrganisation")
  • name string required
  • registry_code string nullable
  • country string nullable
  • role string nullable
• cpv_name string nullable
• dates object nullable
  • @type string (default: "RiigihankedTenderDates")
  • published_at integer nullable
  • deadline_at integer nullable
  • opening_at integer nullable
• notices_count integer nullable
• contracts_count integer nullable
• disputes_count integer nullable
• is_e_procurement boolean nullable
• is_multi_stage boolean nullable
• is_green boolean nullable
• is_suspended boolean nullable
• has_parts boolean nullable
• start_basis string nullable
• country string (default: "EE")
• 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 — 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.