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
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.
Result
- total_count:
- 1
- hits:
1 results
- id:
- 2020-354008
- buyer:
1 results
- id:
- 3e6cca67e0586c20567c6349931f6b2e
- organization_id:
- 984 661 177
- name:
- Vygruppen AS
- heading:
- Order Managment System
- description:
- Vy strives to make it easy for end users to travel in an environmentally friendly way and use public transportation. Vy have established a mobility strategy with the aim to provide a door to door journeys to our consumers. Such journeys will consist of one or more modes of transport, also known as multi-modal trips, with transport products delivered both by Vy and collaborating transportation partners. Essential to providing the best consumer experience for multi-modal journeys is a combined interface for planning and purchase, across the market. The consumer will therefore need to combine parts of a journey in one shopping basket, get an overview and summary of the products and their costs, do adjustments of the selection of products, be offered up-sell/cross-sell and finally pay for all journeys and products in one transaction.
- location_id:
No results.
- estimatedValue:
- not reported by source
- type:
- ANNOUNCEMENT_OF_COMPETITION
- allTypes:
2 results
- ANNOUNCEMENT_OF_COMPETITION
- COMPETITION
- status:
- not reported by source
- issueDate:
- 2020-01-23T10:00:00Z
- deadline:
- not reported by source
- sentToTed:
- yes
- publicationDate:
- 2020-01-23
- placeOfPerformance:
No results.
- procurementStrategicLabels:
No results.
- limit:
- 25
- offset:
- 0
- returned:
- 1
- has_more_results:
- no
- truncated:
- no
Show all fields in HTML
- total_count:
- 1
- hits:
1 results
- id:
- 2020-354008
- buyer:
1 results
- id:
- 3e6cca67e0586c20567c6349931f6b2e
- organization_id:
- 984 661 177
- name:
- Vygruppen AS
- heading:
- Order Managment System
- description:
- Vy strives to make it easy for end users to travel in an environmentally friendly way and use public transportation. Vy have established a mobility strategy with the aim to provide a door to door journeys to our consumers. Such journeys will consist of one or more modes of transport, also known as multi-modal trips, with transport products delivered both by Vy and collaborating transportation partners. Essential to providing the best consumer experience for multi-modal journeys is a combined interface for planning and purchase, across the market. The consumer will therefore need to combine parts of a journey in one shopping basket, get an overview and summary of the products and their costs, do adjustments of the selection of products, be offered up-sell/cross-sell and finally pay for all journeys and products in one transaction.
- location_id:
No results.
- estimatedValue:
- not reported by source
- type:
- ANNOUNCEMENT_OF_COMPETITION
- allTypes:
2 results
- ANNOUNCEMENT_OF_COMPETITION
- COMPETITION
- status:
- not reported by source
- issueDate:
- 2020-01-23T10:00:00Z
- deadline:
- not reported by source
- sentToTed:
- yes
- publicationDate:
- 2020-01-23
- placeOfPerformance:
No results.
- procurementStrategicLabels:
No results.
- limit:
- 25
- offset:
- 0
- returned:
- 1
- has_more_results:
- no
- truncated:
- no
Will you use the result in generated code?
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.