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.

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.
`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&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.

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.

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-11-04T18:19:13Z in 0.130 seconds.

total_count:

hits:

1 results

id:
2026-101904
buyer:
1 results
1. id:
  2d644a8d7ea67e39781f757a74486a01
  organization_id:
  921233418
  name:
  Orkland Kommune
heading:
Intensjonskunngjøring SCADA-system
description:
Orkland kommune har intensjon om å inngå en løpende kontrakt med Autic System AS, for produktet Ignition - SCADA-system for vann- og avløp. Orkland kommune gjennomfører anskaffelsen uten konkurranse da anskaffelsen gjelder ytelser som bare en bestemt leverandør kan levere, fordi konkurranse er umulig av tekniske årsaker, jf. forsyningsforskriften § 9-3 b nr. 2. Ignition er en full webbasert SCADA-plattform, med HMI-klienter levert som rene HTML5 applikasjoner som kan kjøres i standard nettlesere på PC, nettbrett og mobil uten lokal klientinstallasjon eller plugins. Løsningen støtter separate, logisk adskilte prosjekter/instanser innenfor samme plattform, der hvert prosjekt kan administreres, utvikles og driftes uavhengig, men fortsatt under en felles gateway/server. Utviklingsmiljøet som er inkludert i plattformen støtter mer enn 10 samtidige utviklere på samme system/prosjekt uten ekstra lisenskostnader per utvikler eller bruker. SCADA-plattformen er utbredt i markedet, med et dokumentert og bredt økosystem av sertifiserte integratorer og utviklere i Norden og internasjonalt, slik at kommunen ikke er avhengig av én enkelt leverandør, men kan velge mellom flere kompetente miljøer for videreutvikling og drift. Løsningen har innebygd støtte for SAML 2.0 og OpenID Connect som autentiseringsmekanismer, som muliggjør integrasjon med nasjonale ID-løsninger som BankID/Freja samt kommunens øvrige IAM løsning. SCADA-systemet er modulbasert, slik at funksjonalitet som historikk (Historian), rapportering, web HMI, alarmhåndtering, SMS/e postvarsling og edge/IIoT funksjoner leveres som separate moduler innenfor samme plattform, og kan aktiveres/deaktiveres uten å skifte system.
location_id:
1 results
1. anyw
estimatedValue:
not reported by source
type:
ANNOUNCEMENT_OF_INTENT
allTypes:
2 results
1. RESULT
2. ANNOUNCEMENT_OF_INTENT
status:
not reported by source
issueDate:
2026-01-27T07:53:46Z
deadline:
not reported by source
sentToTed:
yes
publicationDate:
2026-01-28
placeOfPerformance:
- Ikke stedbunden
procurementStrategicLabels:
No results.

Show all fields in HTML

total_count:

hits:

1 results

id:
2026-101904
buyer:
1 results
1. id:
  2d644a8d7ea67e39781f757a74486a01
  organization_id:
  921233418
  name:
  Orkland Kommune
heading:
Intensjonskunngjøring SCADA-system
description:
Orkland kommune har intensjon om å inngå en løpende kontrakt med Autic System AS, for produktet Ignition - SCADA-system for vann- og avløp. Orkland kommune gjennomfører anskaffelsen uten konkurranse da anskaffelsen gjelder ytelser som bare en bestemt leverandør kan levere, fordi konkurranse er umulig av tekniske årsaker, jf. forsyningsforskriften § 9-3 b nr. 2. Ignition er en full webbasert SCADA-plattform, med HMI-klienter levert som rene HTML5 applikasjoner som kan kjøres i standard nettlesere på PC, nettbrett og mobil uten lokal klientinstallasjon eller plugins. Løsningen støtter separate, logisk adskilte prosjekter/instanser innenfor samme plattform, der hvert prosjekt kan administreres, utvikles og driftes uavhengig, men fortsatt under en felles gateway/server. Utviklingsmiljøet som er inkludert i plattformen støtter mer enn 10 samtidige utviklere på samme system/prosjekt uten ekstra lisenskostnader per utvikler eller bruker. SCADA-plattformen er utbredt i markedet, med et dokumentert og bredt økosystem av sertifiserte integratorer og utviklere i Norden og internasjonalt, slik at kommunen ikke er avhengig av én enkelt leverandør, men kan velge mellom flere kompetente miljøer for videreutvikling og drift. Løsningen har innebygd støtte for SAML 2.0 og OpenID Connect som autentiseringsmekanismer, som muliggjør integrasjon med nasjonale ID-løsninger som BankID/Freja samt kommunens øvrige IAM løsning. SCADA-systemet er modulbasert, slik at funksjonalitet som historikk (Historian), rapportering, web HMI, alarmhåndtering, SMS/e postvarsling og edge/IIoT funksjoner leveres som separate moduler innenfor samme plattform, og kan aktiveres/deaktiveres uten å skifte system.
location_id:
1 results
1. anyw
estimatedValue:
not reported by source
type:
ANNOUNCEMENT_OF_INTENT
allTypes:
2 results
1. RESULT
2. ANNOUNCEMENT_OF_INTENT
status:
not reported by source
issueDate:
2026-01-27T07:53:46Z
deadline:
not reported by source
sentToTed:
yes
publicationDate:
2026-01-28
placeOfPerformance:
- Ikke stedbunden
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

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.