Europa APIted.europa.eu ↗
Search EU public procurement notices from TED (Tenders Electronic Daily) via a single API endpoint. Returns titles, reference numbers, deadlines, and more.
What is the Europa API?
The TED Europa API provides access to public procurement notices published in the EU's Official Journal supplement via a single search_notices endpoint. Each response returns up to 10 fields per notice — including reference number, title, contracting organization, publication date, and submission deadline — across the full TED database, sorted newest-first. Developers can paginate through results using page and limit parameters with pages of up to 250 notices.
curl -X GET 'https://api.parse.bot/scraper/9b150839-8197-4f8e-af4d-ea0359875120/search_notices?query=software' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace ted-europa-eu-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: TED Procurement Notices — search EU tenders by keyword."""
from parse_apis.ted_europa_eu_api import Ted, InputFormatInvalid
client = Ted()
# Search for procurement notices about software, capped at 5 results.
for notice in client.notices.search(query="software", limit=5):
deadline = notice.submission_deadline or "no deadline"
print(f"{notice.reference_number} {notice.publication_date:%Y-%m-%d} {deadline}")
print(f" {notice.description_title[:100]}")
print(f" Buyer: {notice.organization_name[:80]}")
# Drill into one notice to inspect its document renditions.
notice = client.notices.search(query="cybersecurity", limit=1).first()
if notice is not None:
print(f"\n--- {notice.reference_number} ---")
print(notice.source_url)
for link in notice.document_links:
print(f" [{link.format}] {link.url}")
# Demonstrate typed error handling for malformed queries.
try:
client.notices.search(query="invalid!@#$", limit=1).first()
except InputFormatInvalid as exc:
print(f"Bad query rejected: {exc.message}")
print("\nexercised: notices.search / Notice fields / DocumentLink fields / InputFormatInvalid")
Full-text keyword search of TED procurement notices, newest publication date first. One notice per row: reference_number is the TED publication number, description_title is the notice title (English text preferred, otherwise the first available language), organization_name is the buyer, publication_date and submission_deadline are ISO dates with offset (submission_deadline is null when the notice has no receipt deadline, e.g. award notices), source_url is the notice's English detail page, and document_links lists the PDF, HTML and XML renditions (empty when none). Multiple keywords are matched together (all must appear). Paginates by page number: page defaults to 1 and limit defaults to 10 (capped at 250); has_more indicates a further page exists against total_count. An unknown keyword returns an empty notices array with total_count 0. One upstream request per call.
| Param | Type | Description |
|---|---|---|
| page | integer | 1-based page number over the result set. |
| limit | integer | Number of notices per page, 1 to 250 (larger values are capped). |
| queryrequired | string | One or more keywords separated by spaces (letters, digits, hyphens, apostrophes, dots). Quotes and operators are rejected. |
{
"type": "object",
"fields": {
"page": "integer page returned",
"limit": "integer page size applied after capping",
"query": "echo of the keyword string searched",
"notices": "array of notice objects: reference_number, description_title, organization_name, publication_date, submission_deadline (nullable), source_url, document_links (array of {format, url})",
"has_more": "boolean, true when page*limit < total_count",
"total_count": "integer total notices matching on TED"
},
"sample": {
"data": {
"page": 1,
"limit": 10,
"query": "software",
"notices": [
{
"source_url": "https://ted.europa.eu/en/notice/-/detail/672036-2026",
"document_links": [
{
"url": "https://ted.europa.eu/en/notice/672036-2026/pdf",
"format": "pdf"
},
{
"url": "https://ted.europa.eu/en/notice/-/detail/672036-2026",
"format": "html"
},
{
"url": "https://ted.europa.eu/en/notice/672036-2026/html",
"format": "htmlDirect"
},
{
"url": "https://ted.europa.eu/en/notice/672036-2026/xml",
"format": "xml"
}
],
"publication_date": "2026-09-30+02:00",
"reference_number": "672036-2026",
"description_title": "Germany – Software package and information systems – Camunda 8 Software-Lizenzen mit Herstellersupport",
"organization_name": "Bundesrepublik Deutschland, vertreten durch das Bundesministerium des Innern, vertreten durch das Beschaffungsamt des BMI",
"submission_deadline": "2026-10-29T11:30:00+01:00"
}
],
"has_more": true,
"total_count": 498109
},
"status": "success"
}
}About the Europa API
What the API Returns
The search_notices endpoint performs full-text keyword search over TED procurement notices and returns a paginated result set sorted by publication date descending. Each notice object includes reference_number (the TED publication identifier), description_title (English text preferred, falling back to the first available language), organization_name (the contracting authority), publication_date, and submission_deadline (nullable — not all notice types carry a deadline). The response envelope also includes total_count, has_more, and an echo of the query and pagination parameters applied.
Querying and Pagination
The required query parameter accepts one or more keywords separated by spaces; letters, digits, hyphens, apostrophes, and dots are supported. The page parameter is 1-based, and limit accepts values from 1 to 250 — values above 250 are capped automatically. Use has_more (true when page * limit < total_count) to drive pagination loops without needing to calculate offsets manually. total_count reflects the full count of matching notices on TED.
Coverage and Freshness
TED publishes notices covering all EU member states and countries bound by the Government Procurement Agreement (GPA), spanning works, supplies, and services contracts above EU threshold values. Notices include contract awards, prior information notices, and calls for tender. The API reflects the live TED publication index, so newly published notices appear as the source is updated.
The Europa API is a managed, monitored endpoint for ted.europa.eu — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when ted.europa.eu changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official ted.europa.eu API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Monitor new contract opportunities in a specific sector by querying product or service keywords and filtering by
publication_date - Track which
organization_nameentities are issuing tenders in a given domain to identify public-sector buyers - Alert procurement teams when
submission_deadlineis within a target window for notices matching their keywords - Aggregate
total_counttrends over time for procurement market sizing research - Build a tender digest newsletter by paginating
search_noticesdaily and collecting newreference_numberentries - Cross-reference
organization_nameagainst a CRM to flag existing clients issuing relevant public tenders - Identify contract award patterns by searching for award-related keywords and recording
publication_datesequences
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does TED (ted.europa.eu) have an official developer API?+
What does the `submission_deadline` field contain, and when is it null?+
submission_deadline contains that date. It is nullable — contract award notices, prior information notices, and some other notice types do not carry a submission deadline, so those objects return null for that field.Does the API support filtering by country, CPV code, or contract type?+
query parameter; filtering by structured fields such as country, CPV code, contract value, or notice type is not available. You can fork the API on Parse and revise it to add endpoint parameters or endpoints that filter on those structured fields.Can I retrieve the full notice text or attached documents through this API?+
reference_number, description_title, organization_name, publication_date, and submission_deadline. Full notice body text and linked procurement documents are not included in the response. You can fork the API on Parse and revise it to add a notice detail endpoint that returns the complete notice content.How deep can I paginate into a result set?+
page parameter is 1-based and works in combination with limit (capped at 250). The has_more boolean tells you whether additional pages exist, and total_count gives the full match count. Very large result sets with thousands of matching notices are traversable, but broad single-keyword queries may return very high total_count values — using more specific multi-keyword queries produces more manageable result sets.