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'; 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&include_placeholders=false&limit=25&offset=0

Replace {query}, {types}, {statuses}, {contract_nature}, {cpv_codes}, {locations}, {buyer}, {winner}, {date_from}, {date_to}, {sort_by}, {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&include_placeholders=false&limit=25&offset=0. Open this exact request as JSON.

ParameterRequirementJSON typeDescription
queryoptionalstringFree-text search (Norwegian or English), e.g. "IT-drift", "snørydding", "rammeavtale konsulent". Start here.
typesoptionalunionFilter 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.
statusesoptionalunionACTIVE (open for bids), EXPIRED, AWARDED, CANCELLED.
contract_natureoptionalunionWORKS, SERVICES and/or SUPPLIES.
cpv_codesoptionalunion8-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.
locationsoptionalunionNUTS-style location ids, e.g. ["NO060"] (Trøndelag), or "anyw" for non-location-bound. See list_location_codes().
buyeroptionalunionBuyer 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.
winneroptionalunionDoffin's internal supplier id (32-hex). Winner names cannot be used - they are not present in search results to resolve against.
date_fromoptionalunionPublication date lower bound, "YYYY-MM-DD".
date_tooptionalunionPublication date upper bound, "YYYY-MM-DD".
sort_byoptionalstringRELEVANCE (default), PUBLICATION_DATE_DESC, PUBLICATION_DATE_ASC, DEADLINE, ESTIMATED_VALUE_ASC, ESTIMATED_VALUE_DESC.
include_placeholdersoptionalbooleanBy 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.
limitoptionalintegerGateway page size; default 25, maximum 100.
offsetoptionalintegerNumber 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&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&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&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.

Type: string. Free-text search (Norwegian or English), e.g. "IT-drift", "snørydding", "rammeavtale konsulent". Start here.
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.
Type: list of string (comma-separated). ACTIVE (open for bids), EXPIRED, AWARDED, CANCELLED.
Type: list of string (comma-separated). WORKS, SERVICES and/or SUPPLIES.
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.
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().
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.
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.
Type: string. Publication date lower bound, "YYYY-MM-DD".
Type: string. Publication date upper bound, "YYYY-MM-DD".
Type: string. RELEVANCE (default), PUBLICATION_DATE_DESC, PUBLICATION_DATE_ASC, DEADLINE, ESTIMATED_VALUE_ASC, ESTIMATED_VALUE_DESC.
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-11-20T13:03:37Z in 0.202 seconds.

total_count:
1
hits:

1 results

  1. id:
    2026-117883
    buyer:

    1 results

    1. id:
      ba604041997d8cf4073f2172ff7182fd
      organization_id:
      987592567
      name:
      Oslo kommune v/ Oslo Havn KF
    heading:
    25HAV26 - Ship to shore container crane - Request for information
    description:
    Oslo Havn KF is a municipal enterprise owned by the City of Oslo, governed by its own board of directors. The enterprise's objective is to ensure efficient and rational port operations to facilitate effective and environmentally friendly maritime transport, to oversee traffic within the municipality’s maritime area, and to manage the port’s properties and infrastructure in a financially and environmentally sound manner. Oslo Havn holds the overall responsibility for the operation of the port and for exercising public authority within the municipality’s maritime areas pursuant to the Norwegian Harbor’s and Fairways Act. Oslo Havn's societal responsibility is to facilitate efficient and environmentally friendly maritime transport to and from Oslo, Norway, while minimizing societal costs through the modernization and development of contemporary port facilities. Oslo Havn operates approximately 10 kilometers of quay infrastructure, including both open pile and solid fill quays, spread across multiple harbor areas. These structures support diverse maritime activities such as container shipping, ro-ro terminals, cruise traffic, urban logistics, and bulk transport. The infrastructure is managed and maintained with a strong emphasis on sustainability and digital transformation. Oslo Havn's vision is to be the world’s most space-efficient and environmentally friendly urban port. Oslo Havn aims to become one of the world’s first zero-emission ports. To support this, Oslo Havn is investing in digital technologies, including underwater and above-water 3D scanning, digital twins, and condition-based maintenance strategies for its quay infrastructure. For more information see https://www.oslohavn.no/en/ [https://www.oslohavn.no/en/] INTRODUCTION AND BACKGROUND FOR THE RFI Oslo Havn owns the ship-to-shore (STS) cranes at the Sjursøya container terminal, which is operated by Yilport Oslo. The terminal currently has four STS cranes. Oslo Havn is planning to procure one new STS crane to replace one of the existing cranes. The new crane shall operate on the existing crane rails, fit between the existing cranes, and serve feeder and short-sea container vessels. The crane shall be delivered fully erected and shall be factory acceptance tested (FAT) before shipment. The table below summarises the main parameters requested for the new crane. The parameters correspond to the existing cranes and quay infrastructure at Sjursøya and are based on Oslo Havn’s draft technical specification. The figures are intended to give suppliers an understanding of the required crane class and are not binding requirements. Suppliers are welcome to comment on the parameters and propose alternative solutions.
    location_id:

    1 results

    1. NO081
    estimatedValue:
    not reported by source
    type:
    ADVISORY_NOTICE
    allTypes:

    2 results

    1. ADVISORY_NOTICE
    2. PLANNING
    status:
    not reported by source
    issueDate:
    2026-11-17T08:36:06Z
    deadline:
    not reported by source
    sentToTed:
    yes
    publicationDate:
    2026-11-18
    placeOfPerformance:
    procurementStrategicLabels:

    No results.

Show all fields in HTML
total_count:
1
hits:

1 results

  1. id:
    2026-117883
    buyer:

    1 results

    1. id:
      ba604041997d8cf4073f2172ff7182fd
      organization_id:
      987592567
      name:
      Oslo kommune v/ Oslo Havn KF
    heading:
    25HAV26 - Ship to shore container crane - Request for information
    description:
    Oslo Havn KF is a municipal enterprise owned by the City of Oslo, governed by its own board of directors. The enterprise's objective is to ensure efficient and rational port operations to facilitate effective and environmentally friendly maritime transport, to oversee traffic within the municipality’s maritime area, and to manage the port’s properties and infrastructure in a financially and environmentally sound manner. Oslo Havn holds the overall responsibility for the operation of the port and for exercising public authority within the municipality’s maritime areas pursuant to the Norwegian Harbor’s and Fairways Act. Oslo Havn's societal responsibility is to facilitate efficient and environmentally friendly maritime transport to and from Oslo, Norway, while minimizing societal costs through the modernization and development of contemporary port facilities. Oslo Havn operates approximately 10 kilometers of quay infrastructure, including both open pile and solid fill quays, spread across multiple harbor areas. These structures support diverse maritime activities such as container shipping, ro-ro terminals, cruise traffic, urban logistics, and bulk transport. The infrastructure is managed and maintained with a strong emphasis on sustainability and digital transformation. Oslo Havn's vision is to be the world’s most space-efficient and environmentally friendly urban port. Oslo Havn aims to become one of the world’s first zero-emission ports. To support this, Oslo Havn is investing in digital technologies, including underwater and above-water 3D scanning, digital twins, and condition-based maintenance strategies for its quay infrastructure. For more information see https://www.oslohavn.no/en/ [https://www.oslohavn.no/en/] INTRODUCTION AND BACKGROUND FOR THE RFI Oslo Havn owns the ship-to-shore (STS) cranes at the Sjursøya container terminal, which is operated by Yilport Oslo. The terminal currently has four STS cranes. Oslo Havn is planning to procure one new STS crane to replace one of the existing cranes. The new crane shall operate on the existing crane rails, fit between the existing cranes, and serve feeder and short-sea container vessels. The crane shall be delivered fully erected and shall be factory acceptance tested (FAT) before shipment. The table below summarises the main parameters requested for the new crane. The parameters correspond to the existing cranes and quay infrastructure at Sjursøya and are based on Oslo Havn’s draft technical specification. The figures are intended to give suppliers an understanding of the required crane class and are not binding requirements. Suppliers are welcome to comment on the parameters and propose alternative solutions.
    location_id:

    1 results

    1. NO081
    estimatedValue:
    not reported by source
    type:
    ADVISORY_NOTICE
    allTypes:

    2 results

    1. ADVISORY_NOTICE
    2. PLANNING
    status:
    not reported by source
    issueDate:
    2026-11-17T08:36:06Z
    deadline:
    not reported by source
    sentToTed:
    yes
    publicationDate:
    2026-11-18
    placeOfPerformance:
    procurementStrategicLabels:

    No 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

  1. Replace the placeholders in the HTML GET template; remove optional parameters you do not need.
  2. Check types, units, limits and ID formats in the parameter table.
  3. 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

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.