search_doffin

Search Norwegian public procurement notices on Doffin.

Signature: search_doffin(query: string, optional, default ''; types: list of string (comma-separated), optional, default None; statuses: list of string (comma-separated), optional, default None; contract_nature: list of string (comma-separated), optional, default None; cpv_codes: list of string (comma-separated), optional, default None; locations: list of string (comma-separated), optional, default None; buyer: list of string (comma-separated), optional, default None; winner: list of string (comma-separated), optional, default None; date_from: string, optional, default None; date_to: string, optional, default None; sort_by: string, optional, default 'RELEVANCE'; page: integer, optional, default 1; hits_per_page: integer, optional, default 10; include_placeholders: yes/no, optional, default False; limit: integer, items, optional, default 25; offset: integer, items, optional, default 0)

Direct GET

For navigating agents: open the HTML page with parameters in the URL. The result is fetched and displayed without screenshots or form filling.

Open this validated HTML GET URL

https://allemannsdata.com/wiki/kilder/doffin/search_doffin/?query=&types={types}&statuses={statuses}&contract_nature={contract_nature}&cpv_codes={cpv_codes}&locations={locations}&buyer={buyer}&winner={winner}&date_from={date_from}&date_to={date_to}&sort_by=RELEVANCE&page=1&hits_per_page=10&include_placeholders=false&limit=25&offset=0

Replace {query}, {types}, {statuses}, {contract_nature}, {cpv_codes}, {locations}, {buyer}, {winner}, {date_from}, {date_to}, {sort_by}, {page}, {hits_per_page}, {include_placeholders} with values. Remove unused optional parameters from the URL.

For software and dashboards: Read the operation descriptor. The JSON GET template is https://allemannsdata.com/wiki/api/v1/kilder/doffin/search_doffin?query=&types={types}&statuses={statuses}&contract_nature={contract_nature}&cpv_codes={cpv_codes}&locations={locations}&buyer={buyer}&winner={winner}&date_from={date_from}&date_to={date_to}&sort_by=RELEVANCE&page=1&hits_per_page=10&include_placeholders=false&limit=25&offset=0. Open this exact request as JSON.

Parameter	Requirement	JSON type	Description
`query`	optional	string	Free-text search (Norwegian or English), e.g. "IT-drift", "snørydding", "rammeavtale konsulent". Start here.
`types`	optional	union	Filter by notice type. Parent types: PLANNING, COMPETITION, RESULT. Specific types: ANNOUNCEMENT_OF_COMPETITION, DYNAMIC_PURCHASING_SCHEME, QUALIFICATION_SCHEME, ANNOUNCEMENT_OF_INTENT, PRE_ANNOUNCEMENT, ADVISORY_NOTICE, NOTICE_ON_BUYER_PROFILE, ANNOUNCEMENT_OF_CONCLUSION_OF_CONTRACT, CHANGE_OF_CONCLUSION_OF_CONTRACT, CANCELLED_OR_MISSING_CONCLUSION_OF_CONTRACT. Use ["COMPETITION"] + statuses=["ACTIVE"] for open tenders.
`statuses`	optional	union	ACTIVE (open for bids), EXPIRED, AWARDED, CANCELLED.
`contract_nature`	optional	union	WORKS, SERVICES and/or SUPPLIES.
`cpv_codes`	optional	union	8-digit CPV codes, e.g. ["45000000"]. Matches the code and its children. Find codes with search_cpv_codes(). Best combined with a free-text query.
`locations`	optional	union	NUTS-style location ids, e.g. ["NO060"] (Trøndelag), or "anyw" for non-location-bound. See list_location_codes().
`buyer`	optional	union	Buyer organization full name(s) exactly as written on notices, e.g. ["Trondheim kommune"]. Resolved to Doffin's internal buyer id via a free-text lookup; names that match no buyer are reported in "note" and, if none match, no results are returned (rather than an unfiltered search). Pass the 32-hex buyer id from a result's buyer field directly to skip the lookup.
`winner`	optional	union	Doffin's internal supplier id (32-hex). Winner names cannot be used - they are not present in search results to resolve against.
`date_from`	optional	union	Publication date lower bound, "YYYY-MM-DD".
`date_to`	optional	union	Publication date upper bound, "YYYY-MM-DD".
`sort_by`	optional	string	RELEVANCE (default), PUBLICATION_DATE_DESC, PUBLICATION_DATE_ASC, DEADLINE, ESTIMATED_VALUE_ASC, ESTIMATED_VALUE_DESC.
`page`	optional	integer	1-based page number.
`hits_per_page`	optional	integer	1-50 (default 10).
`include_placeholders`	optional	boolean	By default, hits whose buyer fields look like unfilled eForm template values (org id 123456789, placeholder buyer names) are dropped from the results as junk. Set True to keep them, each flagged with "possible_placeholder": true.
`limit`	optional	integer	Gateway page size; default 25, maximum 100.
`offset`	optional	integer	Number of list items to skip; default 0.

Generated JavaScript, Python and response structure

Use JSON when the user requests code, machine-readable data, value extraction or further computation. Use the HTML GET page to identify the correct source and verify parameters.

Example for generated JavaScript and Python

https://allemannsdata.com/wiki/api/v1/kilder/doffin/search_doffin?query=&types={types}&statuses={statuses}&contract_nature={contract_nature}&cpv_codes={cpv_codes}&locations={locations}&buyer={buyer}&winner={winner}&date_from={date_from}&date_to={date_to}&sort_by=RELEVANCE&page=1&hits_per_page=10&include_placeholders=false&limit=25&offset=0

Replace URL placeholders and remove unused optional parameters.

JavaScript in a dashboard

const url = "https://allemannsdata.com/wiki/api/v1/kilder/doffin/search_doffin?query=&types={types}&statuses={statuses}&contract_nature={contract_nature}&cpv_codes={cpv_codes}&locations={locations}&buyer={buyer}&winner={winner}&date_from={date_from}&date_to={date_to}&sort_by=RELEVANCE&page=1&hits_per_page=10&include_placeholders=false&limit=25&offset=0";
const response = await fetch(url);
if (!response.ok) {
  const failure = await response.json();
  throw new Error(`${failure.error.code}: ${failure.error.message} ${failure.suggestion}`);
}
const result = await response.json();
const data = result.data;

Python without additional packages

import json
from urllib.request import urlopen

url = "https://allemannsdata.com/wiki/api/v1/kilder/doffin/search_doffin?query=&types={types}&statuses={statuses}&contract_nature={contract_nature}&cpv_codes={cpv_codes}&locations={locations}&buyer={buyer}&winner={winner}&date_from={date_from}&date_to={date_to}&sort_by=RELEVANCE&page=1&hits_per_page=10&include_placeholders=false&limit=25&offset=0"
with urlopen(url) as response:
    result = json.load(response)
data = result["data"]

Response structure

{
  "source": "doffin",
  "operation": "search_doffin",
  "parameters": {},
  "data": {},
  "entities": [],
  "_meta": {"retrieved_at": "...", "sources": [], "cache": {}},
  "_links": {"self": "...", "source": "...", "wiki": "...", "feedback": "..."}
}

Form for manual use

The form is a fallback for people and browser agents that cannot open the GET URL directly.

query Type: string. Free-text search (Norwegian or English), e.g. "IT-drift", "snørydding", "rammeavtale konsulent". Start here.

types Type: list of string (comma-separated). Filter by notice type. Parent types: PLANNING, COMPETITION, RESULT. Specific types: ANNOUNCEMENT_OF_COMPETITION, DYNAMIC_PURCHASING_SCHEME, QUALIFICATION_SCHEME, ANNOUNCEMENT_OF_INTENT, PRE_ANNOUNCEMENT, ADVISORY_NOTICE, NOTICE_ON_BUYER_PROFILE, ANNOUNCEMENT_OF_CONCLUSION_OF_CONTRACT, CHANGE_OF_CONCLUSION_OF_CONTRACT, CANCELLED_OR_MISSING_CONCLUSION_OF_CONTRACT. Use ["COMPETITION"] + statuses=["ACTIVE"] for open tenders.

statuses Type: list of string (comma-separated). ACTIVE (open for bids), EXPIRED, AWARDED, CANCELLED.

contract_nature Type: list of string (comma-separated). WORKS, SERVICES and/or SUPPLIES.

cpv_codes Type: list of string (comma-separated). 8-digit CPV codes, e.g. ["45000000"]. Matches the code and its children. Find codes with search_cpv_codes(). Best combined with a free-text query.

locations Type: list of string (comma-separated). NUTS-style location ids, e.g. ["NO060"] (Trøndelag), or "anyw" for non-location-bound. See list_location_codes().

buyer Type: list of string (comma-separated). Buyer organization full name(s) exactly as written on notices, e.g. ["Trondheim kommune"]. Resolved to Doffin's internal buyer id via a free-text lookup; names that match no buyer are reported in "note" and, if none match, no results are returned (rather than an unfiltered search). Pass the 32-hex buyer id from a result's buyer field directly to skip the lookup.

winner Type: list of string (comma-separated). Doffin's internal supplier id (32-hex). Winner names cannot be used - they are not present in search results to resolve against.

date_from Type: string. Publication date lower bound, "YYYY-MM-DD".

date_to Type: string. Publication date upper bound, "YYYY-MM-DD".

sort_by Type: string. RELEVANCE (default), PUBLICATION_DATE_DESC, PUBLICATION_DATE_ASC, DEADLINE, ESTIMATED_VALUE_ASC, ESTIMATED_VALUE_DESC.

page Type: integer. 1-based page number.

hits_per_page Type: integer. 1-50 (default 10).

include_placeholders Type: yes/no. By default, hits whose buyer fields look like unfilled eForm template values (org id 123456789, placeholder buyer names) are dropped from the results as junk. Set True to keep them, each flagged with "possible_placeholder": true.

Result

Source: Doffin and TED. Retrieved 2026-10-26T08:17:47Z in 0.589 seconds.

total_count:

hits:

3 results

id:
2019-369655
buyer:
1 results
1. id:
  b8ef0d385bfe4ae8d9c0440c0a2f861c
  organization_id:
  00964982031
  name:
  Snåsa Kommune
heading:
Snåsa Sjukeheim - Hovedentreprise med tekniske sideentrepriser
description:
Deler av dagens sjukeheim skal river og erstattes med et nytt tilbygg. Deler av dagens bygningsmasse skal bygges om. Nye utomhusarealer skal opparbeides. Bygningsmessig hovedentreprise med tekniske sideentrepriser. Hovedentreprise inneholder riving, bygningsmessige arbeider, ombygging og utomhusarbeider.
location_id:
No results.
estimatedValue:
not reported by source
type:
ANNOUNCEMENT_OF_CONCLUSION_OF_CONTRACT
allTypes:
2 results
1. RESULT
2. ANNOUNCEMENT_OF_CONCLUSION_OF_CONTRACT
status:
not reported by source
issueDate:
2019-09-17T10:00:00Z
deadline:
not reported by source
sentToTed:
yes
publicationDate:
2019-09-17
placeOfPerformance:
No results.
procurementStrategicLabels:
No results.
id:
2026-115713
buyer:
1 results
1. id:
  e4165db9788246be58adfdc634df52bb
  organization_id:
  988964573
  name:
  Trondheim Renholdsverk AS
heading:
Forespørsel om informasjon (RFI) : Oppsamlingsenheter kildesortering Trondheim sentrum
description:
Trondheim Renholdsverk AS (TRV) ønsker informasjon fra markedet og RFI er en del av forarbeidet til ny anskaffelse jf. LOA § 4 Grunnleggende prinsipper , FOA § 12-1 Forberedende undersøkelser og §12-2 Dialog med leverandører før konkurransen.Som følge av avfallsforskriften §10a, må TRV etablere flere muligheter for kildesortering for beboere i Trondheim sentrum (husholdningsavfall). Disse kalles Midtbypunkt, og skal ha tre fraksjoner: plastemballasje, glass- og metallemballasje og papp og papir. Trondheim sentrum er preget av plassmangel, trange gater og infrastruktur over og under bakken. Med hensyn til bybildet, trafikksikkerhet og universell utforming, er det ønskelig å ha enheter som er så lave som mulig. Estetikk er viktig, TRV ser etter robuste og varige løsninger som er et supplement til omgivelsene. Trondheim Renholdsverk vurderer semi-nedgravde enheter som en av flere mulige løsninger som ikke er i vårt produktsortiment i dag.Leverandøren bes besvare denne forespørsel om informasjon (RFI) ved å fylle ut Vedlegg 02_Svarskjema.Utfylt skjema sendes gjennom kommunikasjonsmodulen i Mercell innen fredag 23.oktober 2026 kl.12:00Se "Vedlegg 01_RFI_oppsamlingsenheter_kildesortering_Trondheim_sentrum" for utfyllende beskrivelse til forespørsel om informasjon(RFI).
location_id:
1 results
1. NO060
estimatedValue:
not reported by source
type:
ADVISORY_NOTICE
allTypes:
2 results
1. PLANNING
2. ADVISORY_NOTICE
status:
not reported by source
issueDate:
2026-10-07T12:36:08Z
deadline:
not reported by source
sentToTed:
yes
publicationDate:
2026-10-09
placeOfPerformance:
- Trøndelag/Trööndelage
procurementStrategicLabels:
No results.
id:
2017-359769
buyer:
1 results
1. id:
  7c4978aaf222e1a13a64adab14076794
  organization_id:
  915 070 434
  name:
  Sporveien Oslo AS
heading:
Request for information for a new CBTC signalling system for Oslo Metro
description:
In 2013 Sporveien Oslo AS performed a concept study (KVU) for a new signaling system for the metro. The conclusion was that a Communication Based Train Control (CBTC) system with a semi-automatic train operation (STO) is the preferred solution. In 2014 Ruter has performed a quality assurance (KS1) of the above mentioned KVU, with the same conclusion. In 2015 Sporveien performed a pre-project (Forprosjekt) resulted in a Steering Document for the project. In 2016 Ruter has performed a quality assurance (KS2) of the above mentioned Steering Document, with a recommendation of the project. This Request For Information (RFI) is a follow-up of RFIs conducted in 2013 and 2015. These RFIs had the focus on defining a scope and a budget for the project. Now Sporveien is preparing for a Request For Quotation (RFQ), and the purpose of this RFI is to get a deeper knowledge on functionality, technology, capacity, implementation, operation, maintenance etc.
location_id:
No results.
estimatedValue:
not reported by source
type:
ANNOUNCEMENT_OF_COMPETITION
allTypes:
2 results
1. ANNOUNCEMENT_OF_COMPETITION
2. COMPETITION
status:
not reported by source
issueDate:
2017-05-31T10:00:00Z
deadline:
not reported by source
sentToTed:
yes
publicationDate:
2017-05-31
placeOfPerformance:
No results.
procurementStrategicLabels:
No results.

limit:

offset:

returned:

has_more_results:

Show all fields in HTML

total_count:

hits:

3 results

id:
2019-369655
buyer:
1 results
1. id:
  b8ef0d385bfe4ae8d9c0440c0a2f861c
  organization_id:
  00964982031
  name:
  Snåsa Kommune
heading:
Snåsa Sjukeheim - Hovedentreprise med tekniske sideentrepriser
description:
Deler av dagens sjukeheim skal river og erstattes med et nytt tilbygg. Deler av dagens bygningsmasse skal bygges om. Nye utomhusarealer skal opparbeides. Bygningsmessig hovedentreprise med tekniske sideentrepriser. Hovedentreprise inneholder riving, bygningsmessige arbeider, ombygging og utomhusarbeider.
location_id:
No results.
estimatedValue:
not reported by source
type:
ANNOUNCEMENT_OF_CONCLUSION_OF_CONTRACT
allTypes:
2 results
1. RESULT
2. ANNOUNCEMENT_OF_CONCLUSION_OF_CONTRACT
status:
not reported by source
issueDate:
2019-09-17T10:00:00Z
deadline:
not reported by source
sentToTed:
yes
publicationDate:
2019-09-17
placeOfPerformance:
No results.
procurementStrategicLabels:
No results.
id:
2026-115713
buyer:
1 results
1. id:
  e4165db9788246be58adfdc634df52bb
  organization_id:
  988964573
  name:
  Trondheim Renholdsverk AS
heading:
Forespørsel om informasjon (RFI) : Oppsamlingsenheter kildesortering Trondheim sentrum
description:
Trondheim Renholdsverk AS (TRV) ønsker informasjon fra markedet og RFI er en del av forarbeidet til ny anskaffelse jf. LOA § 4 Grunnleggende prinsipper , FOA § 12-1 Forberedende undersøkelser og §12-2 Dialog med leverandører før konkurransen.Som følge av avfallsforskriften §10a, må TRV etablere flere muligheter for kildesortering for beboere i Trondheim sentrum (husholdningsavfall). Disse kalles Midtbypunkt, og skal ha tre fraksjoner: plastemballasje, glass- og metallemballasje og papp og papir. Trondheim sentrum er preget av plassmangel, trange gater og infrastruktur over og under bakken. Med hensyn til bybildet, trafikksikkerhet og universell utforming, er det ønskelig å ha enheter som er så lave som mulig. Estetikk er viktig, TRV ser etter robuste og varige løsninger som er et supplement til omgivelsene. Trondheim Renholdsverk vurderer semi-nedgravde enheter som en av flere mulige løsninger som ikke er i vårt produktsortiment i dag.Leverandøren bes besvare denne forespørsel om informasjon (RFI) ved å fylle ut Vedlegg 02_Svarskjema.Utfylt skjema sendes gjennom kommunikasjonsmodulen i Mercell innen fredag 23.oktober 2026 kl.12:00Se "Vedlegg 01_RFI_oppsamlingsenheter_kildesortering_Trondheim_sentrum" for utfyllende beskrivelse til forespørsel om informasjon(RFI).
location_id:
1 results
1. NO060
estimatedValue:
not reported by source
type:
ADVISORY_NOTICE
allTypes:
2 results
1. PLANNING
2. ADVISORY_NOTICE
status:
not reported by source
issueDate:
2026-10-07T12:36:08Z
deadline:
not reported by source
sentToTed:
yes
publicationDate:
2026-10-09
placeOfPerformance:
- Trøndelag/Trööndelage
procurementStrategicLabels:
No results.
id:
2017-359769
buyer:
1 results
1. id:
  7c4978aaf222e1a13a64adab14076794
  organization_id:
  915 070 434
  name:
  Sporveien Oslo AS
heading:
Request for information for a new CBTC signalling system for Oslo Metro
description:
In 2013 Sporveien Oslo AS performed a concept study (KVU) for a new signaling system for the metro. The conclusion was that a Communication Based Train Control (CBTC) system with a semi-automatic train operation (STO) is the preferred solution. In 2014 Ruter has performed a quality assurance (KS1) of the above mentioned KVU, with the same conclusion. In 2015 Sporveien performed a pre-project (Forprosjekt) resulted in a Steering Document for the project. In 2016 Ruter has performed a quality assurance (KS2) of the above mentioned Steering Document, with a recommendation of the project. This Request For Information (RFI) is a follow-up of RFIs conducted in 2013 and 2015. These RFIs had the focus on defining a scope and a budget for the project. Now Sporveien is preparing for a Request For Quotation (RFQ), and the purpose of this RFI is to get a deeper knowledge on functionality, technology, capacity, implementation, operation, maintenance etc.
location_id:
No results.
estimatedValue:
not reported by source
type:
ANNOUNCEMENT_OF_COMPETITION
allTypes:
2 results
1. ANNOUNCEMENT_OF_COMPETITION
2. COMPETITION
status:
not reported by source
issueDate:
2017-05-31T10:00:00Z
deadline:
not reported by source
sentToTed:
yes
publicationDate:
2017-05-31
placeOfPerformance:
No results.
procurementStrategicLabels:
No results.

limit:

offset:

returned:

has_more_results:

Will you use the result in generated code?

Open the same result as JSON

Is data missing or incorrect? Send feedback about this result.

Continue exploring

How an AI agent should use this page

Ground rule: Navigate with HTML GET links to keep explanations and relationships. Use the page's JSON alternative only when concrete values must be extracted, compared or computed.

How to use the search_doffin lookup

Replace the placeholders in the HTML GET template; remove optional parameters you do not need.
Check types, units, limits and ID formats in the parameter table.
Follow linked results to canonical pages before combining sources.

Misreading to avoid: An empty list means "no results for this lookup". An error message or unavailable source does not mean the data does not exist.

Source-specific next step

Follow the notice ID to the canonical page; use CPV and location codes to narrow broad free-text searches.

Go to the source page for other operations. Use the JSON template only after the HTML result shows that the parameters and source are correct.

AI agent? Read the complete navigation and programming guide.