/oeffentlichevergabe/tenders/search

POST /api/oeffentlichevergabe/tenders/search

Price: 20 credits

Search oeffentlichevergabe.de notices — prior information, contract notices, awards, voluntary ex-ante notices and contract modifications from every German contracting authority and procurement platform, national below-threshold notices included — by keyword, title, buyer, platform, notice type, legal basis, procedure type, contract nature, SME suitability, CPV and NUTS codes, open state, estimated value, publication date and deadline, with the buyers, lots, CPV codes, places of performance and deadlines of each notice.

How to use it

Each row is one notice with the lots the query matched; a query reaches at most its first 10,000 lots, so narrow a wide search with published_from/published_to or notice_type to reach older notices. legal_basis vob_a, vol_a, uvgo and budget_law select the national below-threshold notices. Pass the id of a row to oeffentlichevergabe/tenders for the full notice with organisations, lots, results and winners.

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: 5000)
• keyword string nullable — Full-text keyword or words (examples: "Reinigung"; minLength: 1)
• keyword_mode string nullable — Whether every word or any word must match (one of: "all", "any")
• buyer array nullable — Exact buyer names (examples: ["Stadt Augsburg"]; minItems: 1)
• buyer_keyword string nullable — Word in the buyer name or address (examples: "Augsburg"; minLength: 1)
• platform array nullable — Procurement platforms the notice came from (examples: ["service.bund.de"]; minItems: 1)
• notice_type array nullable — eForms notice types to include (one of: "pin-only", "pin-buyer", "pin-rtl", "pin-tran", "pin-cfc-standard", "pin-cfc-social", "qu-sy", "cn-standard", "cn-social", "cn-desg", "veat", "can-standard", "can-social", "can-desg", "can-tran", "can-modif", "pmc"; minItems: 1)
• legal_basis array nullable — Legal bases to include (one of: "public_contracts_directive", "defence_directive", "utilities_directive", "concessions_directive", "public_transport_regulation", "uvgo", "vob_a", "vol_a", "budget_law", "other"; minItems: 1)
• procedure_type array nullable — Procedure types to include (one of: "open", "restricted", "comp-dial", "comp-tend", "neg-w-call", "neg-wo-call", "innovation", "oth-single", "oth-mult", "de-open", "de-restricted-w-call", "de-restricted-wo-call", "de-comp-w-call", "de-comp-wo-call", "de-comp-neg-w-call", "de-comp-neg-wo-call"; minItems: 1)
• contract_nature array nullable — Contract natures to include (one of: "works", "services", "supplies"; minItems: 1)
• suitable_for array nullable — Business kinds the buyer marked the lot as suitable for (one of: "sme", "freelancers", "self_employed", "startups"; minItems: 1)
• cpv array nullable — CPV codes or code prefixes (examples: ["45"], ["90910000"]; minItems: 1)
• nuts array nullable — NUTS codes or prefixes of the place of performance (examples: ["DE3"], ["DE212"])
• is_open boolean nullable — Only notices still open, or only closed ones
• value_from integer nullable — Minimum estimated value in EUR (examples: 1000000; min: 0)
• value_to integer nullable — Maximum estimated value in EUR (examples: 10000; min: 0)
• published_from string nullable — Earliest publication date, inclusive (examples: "2026-09-01")
• published_to string nullable — Latest publication date, inclusive (examples: "2026-09-21")
• deadline_from string nullable — Earliest deadline date, inclusive (examples: "2026-10-01")
• deadline_to string nullable — Latest deadline date, inclusive (examples: "2026-10-31")
• procedure_id string nullable — Procedure id shared by the notices of one procedure (examples: "e1ea8a27-0d99-45a5-9241-3443adc4e5a4")
• sort string nullable — Result order (one of: "newest", "oldest", "deadline_soonest", "deadline_latest")

Response

• @type string (default: "OeffentlichevergabeTenderSummary")
• id string required
• version string nullable
• original_notice_id string nullable
• procedure_id string nullable
• internal_id string nullable
• notice_type string nullable
• buyer object nullable
  • @type string (default: "OeffentlichevergabeBuyerName")
  • name string required
• buyers array (default: [])
  • @type string (default: "OeffentlichevergabeBuyerName")
  • name string required
• cpv array (default: [])
• lots array (default: [])
  • @type string (default: "OeffentlichevergabeLotSummary")
  • id string required
  • cpv string nullable
  • contract_nature string nullable
  • additional_natures array (default: [])
  • strategic_procurement array (default: [])
  • places array (default: [])
    • @type string (default: "OeffentlichevergabePlace")
    • street string nullable
    • street_additional string nullable
    • city string nullable
    • postcode string nullable
    • nuts string nullable
    • country string nullable
    • other string nullable
    • additional_information string nullable
  • deadline_at integer nullable
  • first_deadline_at integer nullable
  • requests_deadline_at integer nullable
  • expressions_deadline_at integer nullable
  • answers_deadline_at integer nullable
• dates object nullable
  • @type string (default: "OeffentlichevergabeDates")
  • published_at integer nullable
  • issued_at integer nullable
  • changed_at integer nullable
  • preferred_publication_date string nullable
  • future_notice_date string nullable
  • ted_published_date string nullable
  • ted_submitted_at integer nullable
  • deadline_at integer nullable
  • requests_deadline_at integer nullable
  • expressions_deadline_at integer nullable
  • answers_deadline_at integer nullable
• eforms_version string nullable
• country string (default: "DE")
• url string required

Errors

• 422 — A filter value oeffentlichevergabe.de does not accept 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.