search_ted
Search TED (Tenders Electronic Daily) - EU-wide public procurement notices - with the TED Search API v3 expert query syntax.
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.
https://allemannsdata.com/wiki/kilder/doffin/search_ted/?query={query}&fields={fields}&page=1&limit=10&offset=0
For software and dashboards:
Read the operation descriptor.
The JSON GET template is https://allemannsdata.com/wiki/api/v1/kilder/doffin/search_ted?query={query}&fields={fields}&page=1&limit=10&offset=0.
| Parameter | Requirement | JSON type | Description |
|---|---|---|---|
query | required | string | Expert query. Every field condition must be joined with an explicit AND/OR/NOT - there is no implicit operator, so two conditions with nothing between them is a syntax error, not an OR. Append "SORT BY <field> DESC|ASC". Useful fields: - classification-cpv IN (45000000) filter by SUBJECT. Use this, not FT, to restrict to a procurement category. Matches notices tagged with that exact code (a code, not its children); a notice carries several CPVs, so a hit may also cover other things. - FT="text" free text - matches any notice that MENTIONS the words anywhere, so it returns unrelated notices (a construction tender that happens to say "software"). Not a category filter; AND it with classification-cpv to scope. - place-of-performance IN (NOR) ISO 3166 alpha-3 or NUTS codes - buyer-country IN (SWE DNK) - publication-date >= 20260101 or e.g. today(-30) - deadline-receipt-tender-date-lot >= today() - notice-type IN (cn-standard) cn=competition, can=award, pin=prior information; cn-standard, can-standard etc. - contract-nature IN (works services supplies) - buyer-name ~ ("kommune") Example - open Swedish construction tenders: (buyer-country IN (SWE)) AND (classification-cpv IN (45000000)) AND (notice-type IN (cn-standard)) SORT BY publication-date DESC |
fields | optional | union | Response fields to return (defaults cover number, title, buyer, dates, CPV, type, nature, value). |
page | optional | integer | 1-based page (max 15,000 notices reachable via paging). |
limit | optional | integer | 1-250 notices per page (default 10). |
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_ted?query={query}&fields={fields}&page=1&limit=10&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_ted?query={query}&fields={fields}&page=1&limit=10&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_ted?query={query}&fields={fields}&page=1&limit=10&offset=0"
with urlopen(url) as response:
result = json.load(response)
data = result["data"]
Response structure
{
"source": "doffin",
"operation": "search_ted",
"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.
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_ted 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.