Public tender monitoring across EU and national portals

Notice ID and notice type

Distinguishes a contract notice from a prior information notice, a corrigendum or an award. The type decides whether the record opens, changes or closes an opportunity.

Buyer name, country and region

The filter most bid teams sort by. Store the buyer's own identifier where the portal prints one, so the same authority matches across portals.

CPV codes

The Common Procurement Vocabulary is how notices are classified by subject. Matching on CPV codes is far more reliable than keyword matching on titles in 24 languages.

Estimated value and lots

Qualifies the opportunity. Lots matter because a supplier can often bid for one lot of a tender it could never deliver whole.

Procedure type

Open, restricted, negotiated or a framework call-off. It tells the bid team how much work a response will take and whether they can still enter.

Submission deadline and its history

The field corrigenda change most often. Keep every value with the date you saw it, not just the latest.

Document and portal links

Where the bid team goes next. Store the link, not the documents; downloads often require a supplier account.

Award details

Winner, value and number of bids received, from award notices. This is the raw material for win-rate and competitor analysis.

1. 01

   Take TED from the API, not the website

   Query published notices through the TED Search API by CPV code, country and publication date, or load the daily open-data packages. Both are free and neither needs a proxy. Record the notice IDs so you can recognise the same tender on a national portal later.

2. 02

   List the national and regional portals per country

   For each target country, list the national portal, the regional platforms and any large buyers' own profiles. Check which offer RSS feeds, open-data exports or an API; use those first and crawl only what is left.

3. 03

   Sweep each portal's latest notices from inside its country

   Fetch the newest-first listing through an exit in the portal's country, page until you reach notices you already hold, and stop. One sticky session per portal keeps any search state on one address.

   Incremental sweep of one national portal24 linescopy

   import timeimport httpxGATEWAY, PASSWORD = "proxy.arcproxies.io:8000", "PASSWORD"def portal_client(country: str, portal: str) -> httpx.Client:    # Sticky ISP exit in the portal's country, one handle per portal    user = f"USERNAME_pool-arc_country-{country}_session-{portal}_sesstime-15"    return httpx.Client(proxy=f"http://{user}:{PASSWORD}@{GATEWAY}", timeout=30)def new_notices(client: httpx.Client, url: str, seen: set[str]):    page = 1    while True:        r = client.get(url, params={"sort": "published-desc", "page": page})        if r.status_code == 429:            time.sleep(int(r.headers.get("Retry-After", 60)))            continue        ids = parse_notice_ids(r.text)  # your parser for this portal        fresh = [i for i in ids if i not in seen]        yield from fresh        if len(fresh) < len(ids) or not ids:            break  # reached notices we already hold        page += 1        time.sleep(3)  # a small public server: be slow

4. 04

   Re-check open notices for corrigenda

   Once a day, revisit every notice whose deadline has not passed. Store a changed deadline, a new lot or a cancellation as a new version of the record and alert on it as a change, not as a new tender.

5. 05

   Match across portals, then alert

   Join national notices to TED notices on buyer, normalised title, estimated value and deadline. Alert once per tender, with links to every place it is published.

Prices are list prices in EUR, excl. VAT. Volume discounts apply automatically at checkout — full ladder on the pricing page.