Hungary Procurement Monitor — EKR & National Tenders

What does this Actor do?

Hungary Procurement Monitor searches Hungarian national public procurement notices — the layer that sits below EU TED thresholds and is published through EKR (Elektronikus Közbeszerzési Rendszer).

It queries the public TendersGuru Hungary API, which indexes notices from Hungarian procurement sources, and returns normalized JSON you can filter, schedule, and integrate.

Pair it with my EU TED Tender Scraper for complete Hungary coverage:

• TED → above-threshold EU notices
• This Actor → national / below-threshold EKR layer

No login, no API key, no browser. Only public notice metadata.

Ready-to-run examples (no setup)

• Open Hungarian IT tenders (CPV 72)
• Open Hungarian healthcare tenders (CPV 85)

Pair with EU TED Tender Scraper for full Hungary coverage (EU + national layer).

Why use it?

• Find municipal, hospital, and university tenders that never appear on TED
• Filter by Hungarian keywords, CPV codes, notice type, and publication dates
• Export JSON / CSV / Excel or consume via Apify API, webhooks, Make, n8n, or MCP agents
• Pay-per-event pricing — predictable cost per notice for daily monitoring runs

What data can it extract?

Field	Type	Description
noticeId	string	Notice identifier from the source API
tenderId	string	Parent tender/procedure ID when available
source	string	Data source tag (tendersguru-hu)
sourceUrl	string	Link to the notice in the source API
ekrUrl	string	Direct EKR link when the source provides one
titleHu	string	Notice title (Hungarian)
descriptionHu	string	Notice description when published
buyerName	string	Contracting authority / buyer name
cpvCodes	string[]	CPV codes attached to the notice
noticeType	string	Notice type token from the source
publicationDate	string	Publication date (YYYY-MM-DD)
submissionDeadline	string	Submission deadline when published
isOpen	boolean	true if deadline is today or in the future (or unknown)
estimatedValue	object	{ amount, currency } when published
scrapedAt	string	UTC timestamp when stored

Not every notice includes every field. Missing values are null or [].

How to use

1. Open the Input tab.
2. Add optional Keywords (Hungarian or English, e.g. informatika, építés).
3. Add optional CPV codes (prefix match, e.g. 72 for IT services).
4. Optionally restrict Notice types or enable Only open tenders.
5. Set Maximum notices (1–500, default 50).
6. Run the Actor. Results appear in the default dataset.

Local test (Apify CLI):

cd hungary-procurement-monitor
apify run --input-file example_input.json

Input

Field	Required	Default	Notes
keywords	no	—	OR-combined substring match in title, description, buyer
cpvCodes	no	—	Prefix match against notice CPV codes
noticeTypes	no	—	contract_notice, award_notice, prior_info, modification
onlyOpenTenders	no	false	Skip notices with past submission deadline
maxItems	no	50	Integer 1–500
dateFrom	no	—	Inclusive publication date YYYY-MM-DD
dateTo	no	—	Inclusive publication date YYYY-MM-DD

Example — open IT tenders, max 10:

{
  "keywords": ["informatika", "szoftver"],
  "cpvCodes": ["72"],
  "onlyOpenTenders": true,
  "maxItems": 10
}

Output

Each dataset item is one procurement notice. Download from the Output tab or call:

GET https://api.apify.com/v2/datasets/{datasetId}/items

Pricing

Pay-per-event: each stored notice is charged as event procurement-notice (see Pricing tab after publish).

Suggested platform pricing (set in Apify Console):

• procurement-notice: $0.003 per notice (~$3 / 1,000 notices)
• actor-start: $0.01 per run (optional platform event)

Limitations & compliance

• Reads public procurement notices only — no bid submission, no authenticated EKR access.
• Data is aggregated via TendersGuru; for authoritative EKR documents follow ekrUrl / sourceUrl links.
• Source API pagination and field coverage may change; the Actor uses defensive parsing.
• Respect source rate limits; the Actor retries on transient HTTP errors and sleeps between pages.

Related Actors

• EU TED Tender Scraper — above-threshold EU notices
• eMAG Price Watcher — HU/RO e-commerce price monitoring

Support

Open an issue on the Actor page or contact the author via Apify Console.