EU Maritime & Port Opportunity Monitor

Monitor EU maritime tenders, port procurement, public contracts, and funding signals through one API-first Apify Actor. It finds technically relevant opportunities in official Spanish and European Union data, applies a deterministic maritime taxonomy, and emits traceable lifecycle changes for CRM, bid/no-bid, market-intelligence, and business-development workflows.

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

The maritime procurement monitor 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.

Availability verified 2026-09-02: build 0.1.9 succeeded and a bounded TED smoke run completed with five normalized notices, one qualified event, and no errors. The earlier Under maintenance Store notice has been cleared. Validate representative countries, sources, filters, and budgets before scheduling a production dependency.

Start small: use a stable monitorId, select the official sources and countries you need, then run a small representative scan. The first successful observation can emit NEW events; later runs with the same monitorId emit only newly qualified or materially changed opportunities.

Maritime tender monitoring use cases

• Feed new port tenders and deadline changes into a CRM or bid pipeline.
• Track dredging, breakwater, quay, berth, terminal, VTS, and port-safety contracts.
• Find shore-power, alternative-fuel, and port-decarbonisation opportunities.
• Monitor pre-tender consultations before formal procurement opens.
• Follow awards and cancellations for competitor and market intelligence.
• Combine Spanish PLACSP notices, EU TED procurement, and Funding & Tenders signals in one dataset.
• Schedule country, region, CPV, budget, and keyword-specific monitors for business-development teams.

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

Source	Signals	Interface
PLACSP	Spanish preliminary consultations, tenders, awards and cancellations	Official Atom/XML open data
TED	EU procurement notices and awards	Official Search API v3
EU Funding & Tenders	Calls and funded-project signals that may precede procurement	Official 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
}

Input fields

Field	Type	Required	Default	Limits and behavior
monitorId	string	Yes	—	Stable state key, 3–80 characters: letters, numbers, _, or -.
sources	string[]	No	all three	One or more of placsp, ted, funding_tenders; maximum 3.
countries	string[]	No	["ES"]	ISO alpha-2 codes; 1–30 unique values.
regions	string[]	No	[]	Maximum 50. Use NUTS codes such as ES51 when TED is selected; free-form names are not portable across sources.
cpvCodes	string[]	No	[]	Maximum 100. Use complete 8-digit CPV codes such as 45241000 when TED is selected; short roots are not portable across sources.
keywords	string[]	No	[]	Extra Spanish or English terms; maximum 100.
minBudget	number	No	—	Minimum published budget. Records without a budget are excluded when set.
publishedAfter	string	No	previous 30 days	ISO date in YYYY-MM-DD format.
signalTypes	string[]	No	[] (all)	Any of PRE_TENDER, OPEN, AWARDED, CANCELLED, FUNDED_PROJECT, UNKNOWN.
maxResults	integer	No	100	1–1,000 qualified results per run.
minRelevanceScore	number	No	0.35	Deterministic classifier threshold from 0 to 1.
requestTimeoutSeconds	integer	No	30	5–120 seconds for each official-source request.
maxConcurrency	integer	No	3	1–3 official sources queried concurrently.

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.

TED's query API expects NUTS-like subdivision codes and complete CPV values. PLACSP can compare exact source region names or codes, while Funding & Tenders applies its own source values and CPV-prefix filtering. For a monitor that combines sources, NUTS codes and complete 8-digit CPV codes are the safest common input. A syntactically accepted free-form value can still be rejected by an upstream API.

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. The following item is the exact serialized output produced by the v0.1 transition and event-building runtime for a deterministic TED fixture. It documents the response contract, not a current live notice or a performance claim; source data and matched rules can change between runs.

{
  "recordType": "OPPORTUNITY_EVENT",
  "schemaVersion": "1.0",
  "eventType": "NEW",
  "opportunityId": "ted:123456-2026",
  "projectKey": "sha256:1c26485c91b370eb0d15814768250911fbfc04a65b1c41a980e39de4a25a2fec",
  "source": "ted",
  "sourceRecordId": "123456-2026",
  "title": "Shore-side electricity installation at the port",
  "description": null,
  "phase": "OPEN",
  "buyer": "Port Authority",
  "supplier": null,
  "countries": ["ES"],
  "regions": [],
  "cpvCodes": ["45241600"],
  "budgetValue": 3200000.0,
  "budgetCurrency": "EUR",
  "publishedAt": "2026-08-09T10:00:00+00:00",
  "deadlineAt": "2026-10-15T12:00:00+00:00",
  "relevanceScore": 1.0,
  "matchedRules": [
    "category:port_infrastructure",
    "keyword:port",
    "cpv:45241600",
    "score:CPV_MATCH",
    "score:TITLE_TERM",
    "score:BUYER_TERM",
    "score:MULTI_SIGNAL"
  ],
  "changedFields": [],
  "sourceUrl": "https://api.ted.europa.eu/v3/notices/123456-2026",
  "noticeUrl": "https://ted.europa.eu/en/notice/-/detail/123456-2026",
  "sourceEvidence": [
    {
      "source": "ted",
      "sourceRecordId": "123456-2026",
      "sourceUrl": "https://api.ted.europa.eu/v3/notices/123456-2026",
      "noticeUrl": "https://ted.europa.eu/en/notice/-/detail/123456-2026"
    }
  ],
  "firstSeenAt": "2026-08-09T10:00:00+00:00",
  "lastSeenAt": "2026-08-09T10:00:00+00:00"
}

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.

Output fields

Field group	What it contains
Identity	opportunityId, cross-source projectKey, source, and sourceRecordId.
Change	eventType, phase, changedFields, firstSeenAt, and lastSeenAt.
Opportunity	title, optional description, buyer, supplier, countries, regions, CPV codes, budget, publication date, and deadline.
Qualification	Deterministic relevanceScore and the exact matchedRules; this is not a probability of winning.
Provenance	sourceUrl, optional noticeUrl, and sourceEvidence[] for verification against official data.

A repeat scan can legitimately return an empty Dataset when no new or materially changed qualified opportunity is observed. Inspect RUN_SUMMARY to distinguish “no changes” from partial or failed source coverage.

Pricing

The Actor uses two Pay-Per-Event charges:

• 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. When checked on 2026-09-02, the Store showed Apify platform usage as included in the event pricing. Review the current Pricing tab and run a representative sample before scheduling a production monitor because pricing can change.

API integrations

The synchronous REST endpoint returns the default Dataset as a JSON array. These examples call the Actor and process lifecycle events rather than only printing the raw response. Set APIFY_TOKEN in your environment and keep monitorId stable across scheduled runs of the same commercial profile.

cURL

set -o pipefail

curl --fail-with-body -X POST \
  "https://api.apify.com/v2/actors/dekaz~eu-maritime-port-opportunity-monitor/run-sync-get-dataset-items?clean=true" \
  -H "Authorization: Bearer ${APIFY_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{
    "monitorId": "iberian-port-works",
    "countries": ["ES", "PT"],
    "keywords": ["dragado", "shore power"],
    "signalTypes": ["PRE_TENDER", "OPEN", "AWARDED"],
    "maxResults": 100
  }' |
  jq '[.[] | {
    eventType,
    title,
    buyer,
    phase,
    budgetValue,
    deadlineAt,
    relevanceScore,
    noticeUrl
  }]'

Python

Install the official client with pip install apify-client:

import os

from apify_client import ApifyClient


client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("dekaz/eu-maritime-port-opportunity-monitor").call(
    run_input={
        "monitorId": "iberian-port-works",
        "countries": ["ES", "PT"],
        "keywords": ["dragado", "shore power"],
        "signalTypes": ["PRE_TENDER", "OPEN", "AWARDED"],
        "maxResults": 100,
    }
)

if run is None or run.get("status") != "SUCCEEDED":
    status = None if run is None else run.get("status")
    raise RuntimeError(f"The Actor run did not succeed: {status}")

events = list(client.dataset(run["defaultDatasetId"]).iterate_items())
for event in events:
    crm_record = {
        "external_id": event["opportunityId"],
        "change": event["eventType"],
        "title": event["title"],
        "buyer": event.get("buyer"),
        "deadline": event.get("deadlineAt"),
        "source_url": event.get("noticeUrl") or event["sourceUrl"],
    }
    print(crm_record)

if not events:
    print("No new or materially changed qualified opportunities")

Node.js

Node.js 18 or newer includes fetch. Save this ESM example as monitor.mjs and run it with node monitor.mjs:

const endpoint = new URL(
  "https://api.apify.com/v2/actors/dekaz~eu-maritime-port-opportunity-monitor/run-sync-get-dataset-items",
);
endpoint.searchParams.set("clean", "true");

const response = await fetch(endpoint, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.APIFY_TOKEN}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    monitorId: "iberian-port-works",
    countries: ["ES", "PT"],
    keywords: ["dragado", "shore power"],
    signalTypes: ["PRE_TENDER", "OPEN", "AWARDED"],
    maxResults: 100,
  }),
  signal: AbortSignal.timeout(310_000),
});

if (!response.ok) {
  throw new Error(`Apify ${response.status}: ${await response.text()}`);
}

const events = await response.json();
const crmRecords = events.map((event) => ({
  externalId: event.opportunityId,
  change: event.eventType,
  title: event.title,
  buyer: event.buyer,
  deadline: event.deadlineAt,
  sourceUrl: event.noticeUrl ?? event.sourceUrl,
}));

console.log(crmRecords);

Scheduling and no-change runs

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.