/doffin/tenders/search

POST /api/doffin/tenders/search

Price: 20 credits

Search Doffin notices — planning notices, competitions, dynamic purchasing schemes, contract awards and cancellations from every Norwegian contracting authority, national below-threshold notices included — by keyword, competition status, notice type, contract nature, strategic label, place of performance, CPV code, buyer, winner and publication date, with the buyer, estimated value, key dates and status of each notice.

How to use it

A query returns at most its first 1,000 hits, so narrow a wide search with date_from/date_to or notice_type to reach the tail. status applies to competition notices only — planning and result notices carry none — and buyer and supplier take the ids that doffin/buyers/search and doffin/suppliers/search return, not names. Use the id of a row with doffin/tenders for the full notice.

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: 1000)
• keyword string nullable — Full-text keyword (examples: "renhold"; minLength: 1)
• status array nullable — Competition statuses to include (one of: "active", "expired", "awarded", "cancelled"; minItems: 1)
• notice_type array nullable — Notice types to include, a stage or a specific form (one of: "planning", "competition", "result", "notice_on_buyer_profile", "advisory_notice", "pre_announcement", "qualification_scheme", "announcement_of_competition", "dynamic_purchasing_scheme", "announcement_of_intent", "announcement_of_conclusion_of_contract", "change_of_conclusion_of_contract", "cancelled_or_missing_conclusion_of_contract"; minItems: 1)
• contract_nature array nullable — Contract natures to include (one of: "services", "supplies", "works"; minItems: 1)
• strategic_label array nullable — Strategic procurement labels to include (one of: "environment", "social", "innovative"; minItems: 1)
• location array nullable — Place-of-performance codes (examples: ["NO081"], ["anyw"]; minItems: 1)
• cpv array nullable — CPV codes (examples: ["45000000"], ["90900000","90910000"]; minItems: 1)
• buyer array nullable — Buyer ids from doffin/buyers/search (examples: ["e4165db9788246be58adfdc634df52bb"])
• supplier array nullable — Winner ids from doffin/suppliers/search (examples: ["ec3d5c40af90463aed50baea29498830"])
• date_from string nullable — Earliest publication date, inclusive (examples: "2026-09-01")
• date_to string nullable — Latest publication date, inclusive (examples: "2026-09-21")
• sort string nullable — Result order (one of: "relevance", "newest", "oldest", "deadline", "value_ascending", "value_descending")

Response

• @type string (default: "DoffinTenderSummary")
• id string required
• description string nullable
• notice_type string nullable
• notice_types array (default: [])
• stage string nullable
• status string nullable
• buyer object nullable
  • @type string (default: "DoffinBuyer")
  • id string nullable
  • organization_number string nullable
  • name string required
• buyers array (default: [])
  • @type string (default: "DoffinBuyer")
  • id string nullable
  • organization_number string nullable
  • name string required
• value object nullable
  • @type string (default: "DoffinValue")
  • amount number nullable
  • currency string nullable
  • text string nullable
• dates object nullable
  • @type string (default: "DoffinDates")
  • published string nullable
  • issued_at integer nullable
  • deadline_at integer nullable
  • qualification_deadline_at integer nullable
  • planned_ted_publication string nullable
  • preferred_ted_publication string nullable
• location_ids array (default: [])
• places_of_performance array (default: [])
• strategic_labels array (default: [])
• sent_to_ted boolean nullable
• country string (default: "NO")
• 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.