/tenderned/tenders/search

POST /api/tenderned/tenders/search

Price: 20 credits

Search TenderNed publications — market consultations, prior information notices, contract notices, rectifications, awards and contract modifications from every Dutch contracting authority, national below-threshold procedures included — by keyword, notice type, contract type, national or European scope, contract nature, procedure, buyer kind, CPV and NUTS codes, buyer, publication date and closing date, with the buyer, procedure, contract type, closing date and third-party platform of each publication.

How to use it

Narrow a wide query with published_from/published_to or notice_type rather than paging deep; the register holds no status filter, so use deadline=open for procedures still accepting tenders. buyer takes the id from tenderned/buyers/search, not a name. Pass the id of a row to tenderned/tenders for the full notice with lots, values, winners and organisations.

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 — Full-text keyword (examples: "schoonmaak"; minLength: 1)
• notice_type array nullable — Notice types to include (one of: "market_consultation", "prior_information", "contract_notice", "rectification", "award", "modification"; minItems: 1)
• contract_type array nullable — Contract types to include (one of: "works", "supplies", "services"; minItems: 1)
• scope array nullable — National or European procedures (one of: "national", "european"; minItems: 1)
• contract_nature array nullable — Contract natures to include (one of: "public_contract", "contract", "framework_agreement", "dynamic_purchasing_system", "concession", "design_contest", "qualification_system"; minItems: 1)
• procedure array nullable — Procedure kinds to include (one of: "open", "restricted", "competitive_dialogue", "negotiated_with_call", "negotiated_without_call", "private", "open_house", "innovation_partnership", "competitive_tendering", "other_multi_stage", "other_single_stage", "expression_of_interest", "market_consultation"; minItems: 1)
• buyer_type array nullable — Contracting authority kinds to include (one of: "central_government", "defence_contractor", "special_rights_entity", "eu_institution", "public_undertaking", "body_governed_by_public_law", "regional_authority", "subsidised_organisation"; minItems: 1)
• cpv array nullable — CPV codes with check digit (examples: ["90000000-7"]; minItems: 1)
• nuts array nullable — NUTS codes of the place of performance (examples: ["NL32"]; minItems: 1)
• buyer string nullable — Buyer id from tenderned/buyers/search (examples: "49937ffb1c5dad2b0c5d012fdecaa882")
• published_from string nullable — Earliest publication date, inclusive (examples: "2026-06-01")
• published_to string nullable — Latest publication date, inclusive (examples: "2026-08-31")
• deadline string nullable — Closing-date window (one of: "today", "tomorrow", "next_7_days", "next_30_days", "next_month", "open", "none")
• deadline_from string nullable — Earliest closing date, inclusive (examples: "2026-10-01")
• deadline_to string nullable — Latest closing date, inclusive (examples: "2026-10-31")
• sort string nullable — Result order (one of: "relevance", "newest")

Response

• @type string (default: "TendernedTenderSummary")
• id string required
• procedure_id string nullable
• description string nullable
• buyer object nullable
  • @type string (default: "TendernedOrganisation")
  • id string nullable
  • name string nullable
  • registration_number string nullable
  • department string nullable
  • size string nullable
  • address string nullable
  • city string nullable
  • postcode string nullable
  • region string nullable
  • region_code string nullable
  • country string nullable
  • contact_name string nullable
  • email string nullable
  • phone string nullable
  • fax string nullable
  • url string nullable
  • roles array (default: [])
  • won_lots array (default: [])
• notice_type object nullable
  • @type string (default: "TendernedCode")
  • code string nullable
  • label string nullable
• notice_code object nullable
  • @type string (default: "TendernedCode")
  • code string nullable
  • label string nullable
• stage string nullable
• status object nullable
  • @type string (default: "TendernedCode")
  • code string nullable
  • label string nullable
• procedure object nullable
  • @type string (default: "TendernedCode")
  • code string nullable
  • label string nullable
• contract_type object nullable
  • @type string (default: "TendernedCode")
  • code string nullable
  • label string nullable
• is_digital boolean nullable
• is_european boolean nullable
• is_early_termination boolean nullable
• is_eforms_change boolean nullable
• duration object nullable
  • @type string (default: "TendernedCode")
  • code string nullable
  • label string nullable
• dates object nullable
  • @type string (default: "TendernedDates")
  • published string nullable
  • published_at integer nullable
  • deadline_at integer nullable
  • days_to_deadline integer nullable
  • market_consultation_deadline_at integer nullable
  • contract_start string nullable
  • contract_end string nullable
• platform object nullable
  • @type string (default: "TendernedPlatform")
  • name string nullable
  • url string nullable
• country string (default: "NL")
• url string required

Errors

• 422 — A filter value TenderNed does not accept — the accepted values are the enum members of the payload 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.