EU Maritime & Port Opportunity Monitor avatar

EU Maritime & Port Opportunity Monitor

Under maintenance

Pricing

from $100.00 / 1,000 monitor scans

Go to Apify Store
EU Maritime & Port Opportunity Monitor

EU Maritime & Port Opportunity Monitor

Under maintenance

Monitor Spanish and EU public tenders and funded projects for ports, dredging, maritime works, coastal protection, terminals, and decarbonization. Classifies, deduplicates, and tracks lifecycle changes.

Pricing

from $100.00 / 1,000 monitor scans

Rating

0.0

(0)

Developer

Progamadores.com

Progamadores.com

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

11 days ago

Last modified

Share

An API-first Apify Actor that finds and monitors technically relevant maritime and port opportunities from official Spanish and European Union data.

This is procurement intelligence for companies bidding for public contracts. It is not a jobs, vacancies, candidates or employment scraper.

The Actor is designed for marine contractors, engineering consultancies, dredging and coastal works specialists, port-equipment suppliers, shore-power providers, terminal operators, and business-development teams. It returns qualified lifecycle events instead of an unfiltered dump of public notices.

What it monitors

  • Port, harbour, quay, berth, jetty, breakwater and terminal works.
  • Dredging, reclamation, coastal protection and marine construction.
  • Mooring, fendering, navigation, VTS/VTMS and port-safety systems.
  • Shore-side electricity, alternative fuels and port decarbonisation.
  • Maritime engineering, geotechnical and environmental services.

The built-in taxonomy combines maritime CPV roots, deterministic Spanish and English terminology, buyer/authority signals and user-supplied filters. Every result includes the matched rules; the Actor does not use an LLM or an opaque win-probability score.

Official sources

SourceSignalsInterface
PLACSPSpanish preliminary consultations, tenders, awards and cancellationsOfficial Atom/XML open data
TEDEU procurement notices and awardsOfficial Search API v3
EU Funding & TendersCalls and funded-project signals that may precede procurementOfficial public Search API

Source documentation: PLACSP open data, TED Search API, and Funding & Tenders APIs.

Input

{
"monitorId": "iberian-port-works",
"sources": ["placsp", "ted", "funding_tenders"],
"countries": ["ES", "PT"],
"regions": [],
"cpvCodes": ["45241000", "45252124"],
"keywords": ["dragado", "shore power"],
"minBudget": 100000,
"publishedAfter": "2026-07-01",
"signalTypes": ["PRE_TENDER", "OPEN", "AWARDED", "FUNDED_PROJECT"],
"maxResults": 100,
"minRelevanceScore": 0.35
}

monitorId is stable state, not a display label. Reusing it compares the new scan with the last successful observation. Use a different ID for a different commercial profile.

When publishedAfter is omitted, the Actor queries the previous 30 days. Inputs are bounded to protect upstream services, run costs and storage.

Output

Each default Dataset item is a traceable change event:

{
"recordType": "OPPORTUNITY_EVENT",
"schemaVersion": "1.0",
"eventType": "NEW",
"opportunityId": "ted:123456-2026",
"projectKey": "sha256:...",
"source": "ted",
"sourceRecordId": "123456-2026",
"title": "Shore-side electricity installation at the port",
"phase": "OPEN",
"buyer": "Port Authority",
"countries": ["ES"],
"cpvCodes": ["45241600"],
"budgetValue": 3200000,
"budgetCurrency": "EUR",
"deadlineAt": "2026-10-15T12:00:00Z",
"relevanceScore": 0.84,
"matchedRules": ["cpv:45241600", "keyword:shore-side electricity"],
"changedFields": [],
"sourceUrl": "https://api.ted.europa.eu/...",
"noticeUrl": "https://ted.europa.eu/...",
"sourceEvidence": [
{
"source": "ted",
"sourceRecordId": "123456-2026",
"sourceUrl": "https://api.ted.europa.eu/...",
"noticeUrl": "https://ted.europa.eu/..."
}
],
"firstSeenAt": "2026-08-09T10:00:00Z",
"lastSeenAt": "2026-08-09T10:00:00Z"
}

Supported change events are:

  • NEW: first qualified observation for this monitor.
  • UPDATED: one or more material fields changed.
  • DEADLINE_CHANGED: the submission deadline changed.
  • AWARDED: the source now reports an award.
  • CANCELLED: the source explicitly reports cancellation.

Absence from a source response is never interpreted as cancellation. Source health and counts are written to the default Key-Value Store under RUN_SUMMARY; historical state and billing markers live in the named store derived from monitorId.

Pricing contract

The private beta uses two Pay-Per-Event names:

  • monitor-scan: USD 0.10 after at least one official source completes successfully.
  • qualified-opportunity: USD 0.01 for each persisted NEW or changed qualified opportunity.

Duplicates, irrelevant records and failed sources are not charged as qualified opportunities. The Actor respects the run spending limit and uses idempotency keys so a restart cannot bill the same event twice. Event prices must be configured in Apify Console before Store publication; the source code defines the names and charging behavior.

Scheduling and integrations

Save the input as an Apify Task and schedule it daily or weekly. The default Dataset can be consumed through the Apify API, Make, Zapier or a run webhook. Webhook delivery is an Apify platform feature; this Actor does not send data to arbitrary user-provided URLs.

Deliberate v1 limits

  • No PDF or tender-document interpretation.
  • No private, authenticated or paid sources.
  • No browser automation or residential proxy.
  • No bid recommendation, legal advice or probability of winning.
  • No assumption that a missing record was cancelled.
  • Published values remain attributable to the official source and should be verified before bidding.

Development

Runtime: Python 3.13 on apify/actor-python:3.13. The code also supports Python 3.12 for local development.

python -m venv .venv
.\.venv\Scripts\python.exe -m pip install -e ".[dev]"
.\.venv\Scripts\python.exe -m ruff check src tests scripts
.\.venv\Scripts\python.exe -m mypy src
.\.venv\Scripts\python.exe -m pytest

Run the real-source smoke script before a release. Fixtures test parser behavior; the smoke run tests the assumptions made about the live official services.

$env:PYTHONUTF8 = "1"
.\.venv\Scripts\python.exe scripts\smoke_sources.py

Architecture

The code separates source adapters from domain qualification and historical state:

official sources -> normalized source records -> maritime classifier
-> cross-source deduplication -> historical diff
-> Dataset / RUN_SUMMARY / PPE

This separation keeps one upstream schema change from changing the public output contract.