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-09-11T23:50:59Z in 0.144 seconds.

total_count:

hits:

3 results

id:
2026-106042
buyer:
1 results
1. id:
  fc0276307e8a85529306bb92803a380c
  organization_id:
  923119159
  name:
  LYSE LUX AS
heading:
Sensor System Procurement
description:
The procurement concerns the establishment of a framework agreement for a sensor system for the collection of traffic and mobility data. The solution will form part of the commercial service offerings of Lyse Lux and Lyse Agon and may be delivered to external customers, including municipalities. The scope includes the supply of sensor hardware and associated software and services, including data access, integration, operation and maintenance. The contracting authority intends to use and operate the solution, including the possibility to provide related services to third parties. The procurement is conducted in accordance with Part III of the Norwegian Public Procurement Regulations, as the estimated contract value exceeds the EEA threshold for goods and services contracts. The procedure is a competitive procedure with negotiation in accordance with Section 13-2. Due to the nature of the procurement, which includes a combination of hardware, software, integration and operational services, the contracting authority is not able to define all technical and contractual aspects in sufficient detail in advance. Furthermore, the solution requires a degree of flexibility and adaptation. Negotiations are therefore considered necessary to ensure an optimal solution.
location_id:
1 results
1. NO0A1
estimatedValue:
currencyCode:
NOK
amount:
5000000.0
type:
ANNOUNCEMENT_OF_COMPETITION
allTypes:
2 results
1. ANNOUNCEMENT_OF_COMPETITION
2. COMPETITION
status:
EXPIRED
issueDate:
2026-03-27T10:35:42Z
deadline:
2026-04-27T10:00:00Z
sentToTed:
yes
publicationDate:
2026-03-30
placeOfPerformance:
- Rogaland
procurementStrategicLabels:
No results.
id:
2026-109826
buyer:
3 results
1. id:
  bed87b482aba566c9511f70f17cf6dc3
  organization_id:
  916075855
  name:
  FORSVARSMATERIELL
2. id:
  bed87b482aba566c9511f70f17cf6dc3
  organization_id:
  972 417 823
  name:
  FORSVARSMATERIELL
3. id:
  bed87b482aba566c9511f70f17cf6dc3
  organization_id:
  972 417 823
  name:
  FORSVARSMATERIELL
heading:
P1223 - Navigation training vessels - Pre-Qualification Phase
description:
The purpose of this procurement is to meet the Norwegian Armed Forces’ need for increased training capacity for navigators in the Royal Norwegian Navy.This procurement covers the design, construction and delivery of two identical training vessels, with an option for two additional vessels (1 + 1) , to the Norwegian Armed Forces. The vessels shall be used for education and training in military practical navigation, in order to ensure that the required competence of future navigators in the Royal Norwegian Navy is maintained and further developed.The training concept is based on a recurring cycle of theoretical instruction, simulator training and practical navigation. The main teaching platform is the navigation system, which must be as close to identical as possible in the simulator and on board the vessels. In this context, the training vessels serve as a platform for bringing the navigation system to sea.The vessels shall be modern, reliable and representative of current standards, with primary emphasis on safe navigation, energy-efficient operation and pedagogical suitability. The vessels shall be built in accordance with civil (DNV) class. They shall be serially built, with a high degree of standardised civil components and subsystems, in order to ensure effective competition and keep operating costs at a low level.Each vessel shall have a length of less than 24 metres, be capable of achieving a minimum speed of 18 knots, and have a total installed engine power of less than 750 kW. The vessels shall be delivered fully equipped, including navigation systems and sensors, as well as the necessary support and documentation package for operation and maintenance.
location_id:
1 results
1. NO0A2
estimatedValue:
not reported by source
type:
ANNOUNCEMENT_OF_COMPETITION
allTypes:
2 results
1. ANNOUNCEMENT_OF_COMPETITION
2. COMPETITION
status:
EXPIRED
issueDate:
2026-06-01T10:37:47Z
deadline:
2026-07-06T10:00:00Z
sentToTed:
yes
publicationDate:
2026-06-02
placeOfPerformance:
- Vestland
procurementStrategicLabels:
No results.
id:
2018-303844
buyer:
1 results
1. id:
  1172c118d3c0d86c04061c211258f772
  organization_id:
  985 198 292
  name:
  Avinor AS
heading:
RFI - passenger flow analysis platform
description:
Avinor is currently planning to establish a passenger flow analysis platform for both operative and commercial purposes , and would like to gather information about sensor- and software based flow analysis systems available in the market. We would like companies offering such systems to reply to this RFI (n the announcement text the term participants is used for companies/suppliers replying to the RFI).
location_id:
No results.
estimatedValue:
not reported by source
type:
ADVISORY_NOTICE
allTypes:
2 results
1. ADVISORY_NOTICE
2. PLANNING
status:
not reported by source
issueDate:
2018-09-05T10:00:00Z
deadline:
not reported by source
sentToTed:
yes
publicationDate:
2018-09-05
placeOfPerformance:
No results.
procurementStrategicLabels:
No results.

limit:

offset:

returned:

has_more_results:

truncated:

Show all fields in HTML

total_count:

hits:

3 results

id:
2026-106042
buyer:
1 results
1. id:
  fc0276307e8a85529306bb92803a380c
  organization_id:
  923119159
  name:
  LYSE LUX AS
heading:
Sensor System Procurement
description:
The procurement concerns the establishment of a framework agreement for a sensor system for the collection of traffic and mobility data. The solution will form part of the commercial service offerings of Lyse Lux and Lyse Agon and may be delivered to external customers, including municipalities. The scope includes the supply of sensor hardware and associated software and services, including data access, integration, operation and maintenance. The contracting authority intends to use and operate the solution, including the possibility to provide related services to third parties. The procurement is conducted in accordance with Part III of the Norwegian Public Procurement Regulations, as the estimated contract value exceeds the EEA threshold for goods and services contracts. The procedure is a competitive procedure with negotiation in accordance with Section 13-2. Due to the nature of the procurement, which includes a combination of hardware, software, integration and operational services, the contracting authority is not able to define all technical and contractual aspects in sufficient detail in advance. Furthermore, the solution requires a degree of flexibility and adaptation. Negotiations are therefore considered necessary to ensure an optimal solution.
location_id:
1 results
1. NO0A1
estimatedValue:
currencyCode:
NOK
amount:
5000000.0
type:
ANNOUNCEMENT_OF_COMPETITION
allTypes:
2 results
1. ANNOUNCEMENT_OF_COMPETITION
2. COMPETITION
status:
EXPIRED
issueDate:
2026-03-27T10:35:42Z
deadline:
2026-04-27T10:00:00Z
sentToTed:
yes
publicationDate:
2026-03-30
placeOfPerformance:
- Rogaland
procurementStrategicLabels:
No results.
id:
2026-109826
buyer:
3 results
1. id:
  bed87b482aba566c9511f70f17cf6dc3
  organization_id:
  916075855
  name:
  FORSVARSMATERIELL
2. id:
  bed87b482aba566c9511f70f17cf6dc3
  organization_id:
  972 417 823
  name:
  FORSVARSMATERIELL
3. id:
  bed87b482aba566c9511f70f17cf6dc3
  organization_id:
  972 417 823
  name:
  FORSVARSMATERIELL
heading:
P1223 - Navigation training vessels - Pre-Qualification Phase
description:
The purpose of this procurement is to meet the Norwegian Armed Forces’ need for increased training capacity for navigators in the Royal Norwegian Navy.This procurement covers the design, construction and delivery of two identical training vessels, with an option for two additional vessels (1 + 1) , to the Norwegian Armed Forces. The vessels shall be used for education and training in military practical navigation, in order to ensure that the required competence of future navigators in the Royal Norwegian Navy is maintained and further developed.The training concept is based on a recurring cycle of theoretical instruction, simulator training and practical navigation. The main teaching platform is the navigation system, which must be as close to identical as possible in the simulator and on board the vessels. In this context, the training vessels serve as a platform for bringing the navigation system to sea.The vessels shall be modern, reliable and representative of current standards, with primary emphasis on safe navigation, energy-efficient operation and pedagogical suitability. The vessels shall be built in accordance with civil (DNV) class. They shall be serially built, with a high degree of standardised civil components and subsystems, in order to ensure effective competition and keep operating costs at a low level.Each vessel shall have a length of less than 24 metres, be capable of achieving a minimum speed of 18 knots, and have a total installed engine power of less than 750 kW. The vessels shall be delivered fully equipped, including navigation systems and sensors, as well as the necessary support and documentation package for operation and maintenance.
location_id:
1 results
1. NO0A2
estimatedValue:
not reported by source
type:
ANNOUNCEMENT_OF_COMPETITION
allTypes:
2 results
1. ANNOUNCEMENT_OF_COMPETITION
2. COMPETITION
status:
EXPIRED
issueDate:
2026-06-01T10:37:47Z
deadline:
2026-07-06T10:00:00Z
sentToTed:
yes
publicationDate:
2026-06-02
placeOfPerformance:
- Vestland
procurementStrategicLabels:
No results.
id:
2018-303844
buyer:
1 results
1. id:
  1172c118d3c0d86c04061c211258f772
  organization_id:
  985 198 292
  name:
  Avinor AS
heading:
RFI - passenger flow analysis platform
description:
Avinor is currently planning to establish a passenger flow analysis platform for both operative and commercial purposes , and would like to gather information about sensor- and software based flow analysis systems available in the market. We would like companies offering such systems to reply to this RFI (n the announcement text the term participants is used for companies/suppliers replying to the RFI).
location_id:
No results.
estimatedValue:
not reported by source
type:
ADVISORY_NOTICE
allTypes:
2 results
1. ADVISORY_NOTICE
2. PLANNING
status:
not reported by source
issueDate:
2018-09-05T10:00:00Z
deadline:
not reported by source
sentToTed:
yes
publicationDate:
2018-09-05
placeOfPerformance:
No results.
procurementStrategicLabels:
No results.

limit:

offset:

returned:

has_more_results:

truncated:

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.