search_doffin

Search Norwegian public procurement notices on Doffin.

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": "..."}
}

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-08-02T18:59:17Z in 0.165 seconds.

total_count:

hits:

1 results

id:
2024-107722
buyer:
1 results
1. id:
  2d20aebe07a30c63c7054478dd4c8496
  organizationId:
  971032081
  name:
  Statens vegvesen
heading:
Lading av driftsentreprenørenes kjøretøy og maskiner langs riksvegnettet
description:
Statens Vegvesen (SVV) ber om innspill i forbindelse med at vi jobber med et notat om mulighetene for lading av driftsentreprenørene sine kjøretøy og maskiner (og gjerne andre kjøretøy og maskiner som jobber for SVV) langs 10600 km med riksveg. Dette gjøres som en del av gjennomføringen av klimahandlingsplanen for Divisjon drift og vedlikehold. Notatet vil ligge til grunn for strategiarbeidet for våre fremtidige kontrakter. Drift og vedlikehold som står for en betydelig andel av divisjonens klimagassutslipp, som skal reduseres med 55 % innen 2030. Vi ønsker innspill knyttet til blant annet ladeinfrastruktur, ladeteknologi og tilgang og utvikling av elektriske maskiner og kjøretøy som kan benyttes til drift og vedlikehold av riksvegnettet samt innspill til mulige forretningsmodeller for ladeinfrastruktur i våre driftskontrakter (og eventuelt andre som har kjøretøy og maskiner som jobber for SVV). The Norwegian Public Roads Administration (SVV) is requesting input as we are working on a memorandum regarding the possibilities for charging the vehicles and machinery of our maintenance contractors (and preferably other vehicles and machinery working for SVV) along 10,600 km of national roads. This is being done as part of the implementation of the climate action plan for the Operations and Maintenance Division. The memorandum will form the basis for the strategic work for our future contracts. Operations and maintenance account for a significant portion of the division's greenhouse gas emissions, which are to be reduced by 55% by 2030. We are seeking input related to, among other things, charging infrastructure, charging technology, and the availability and development of electric machinery and vehicles that can be used for the operation and maintenance of the national road network, as well as input on possible business models for charging infrastructure in our maintenance contracts
locationId:
- NO020
estimatedValue:
not reported by source
type:
ADVISORY_NOTICE
allTypes:
2 results
1. ADVISORY_NOTICE
2. PLANNING
status:
not reported by source
issueDate:
2024-05-22T13:39:40Z
deadline:
not reported by source
sentToTed:
yes
publicationDate:
2024-05-24
placeOfPerformance:
- Innlandet
procurementStrategicLabels:
No results.

limit:

offset:

returned:

has_more_results:

truncated:

Show all fields in HTML

total_count:

hits:

1 results

id:
2024-107722
buyer:
1 results
1. id:
  2d20aebe07a30c63c7054478dd4c8496
  organizationId:
  971032081
  name:
  Statens vegvesen
heading:
Lading av driftsentreprenørenes kjøretøy og maskiner langs riksvegnettet
description:
Statens Vegvesen (SVV) ber om innspill i forbindelse med at vi jobber med et notat om mulighetene for lading av driftsentreprenørene sine kjøretøy og maskiner (og gjerne andre kjøretøy og maskiner som jobber for SVV) langs 10600 km med riksveg. Dette gjøres som en del av gjennomføringen av klimahandlingsplanen for Divisjon drift og vedlikehold. Notatet vil ligge til grunn for strategiarbeidet for våre fremtidige kontrakter. Drift og vedlikehold som står for en betydelig andel av divisjonens klimagassutslipp, som skal reduseres med 55 % innen 2030. Vi ønsker innspill knyttet til blant annet ladeinfrastruktur, ladeteknologi og tilgang og utvikling av elektriske maskiner og kjøretøy som kan benyttes til drift og vedlikehold av riksvegnettet samt innspill til mulige forretningsmodeller for ladeinfrastruktur i våre driftskontrakter (og eventuelt andre som har kjøretøy og maskiner som jobber for SVV). The Norwegian Public Roads Administration (SVV) is requesting input as we are working on a memorandum regarding the possibilities for charging the vehicles and machinery of our maintenance contractors (and preferably other vehicles and machinery working for SVV) along 10,600 km of national roads. This is being done as part of the implementation of the climate action plan for the Operations and Maintenance Division. The memorandum will form the basis for the strategic work for our future contracts. Operations and maintenance account for a significant portion of the division's greenhouse gas emissions, which are to be reduced by 55% by 2030. We are seeking input related to, among other things, charging infrastructure, charging technology, and the availability and development of electric machinery and vehicles that can be used for the operation and maintenance of the national road network, as well as input on possible business models for charging infrastructure in our maintenance contracts
locationId:
- NO020
estimatedValue:
not reported by source
type:
ADVISORY_NOTICE
allTypes:
2 results
1. ADVISORY_NOTICE
2. PLANNING
status:
not reported by source
issueDate:
2024-05-22T13:39:40Z
deadline:
not reported by source
sentToTed:
yes
publicationDate:
2024-05-24
placeOfPerformance:
- Innlandet
procurementStrategicLabels:
No results.

limit:

offset:

returned:

has_more_results:

truncated:

Will you use the result in generated code?

Open the same result as JSON

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.