Find EU & UK Tenders That Match Your Services

EU & UK Tender Scraper - TED, Matching & Alerts

Find EU TED and UK Find a Tender notices matching your services. Filter by CPV, country, keywords and deadlines; get ranked opportunities, buyer details and source links. Schedule new or changed tender alerts.

Describe what your company sells, add your most important phrases and filters, and the Actor returns a ranked dataset of matching EU and UK tenders. Use it for one-off research or schedule it as a recurring opportunity feed.

This is an independent product and is not affiliated with or endorsed by any government institution. Always verify procurement details in the linked notice.

What you get

• Relevant tenders ranked with an explainable fitScore from 0 to 100
• Clear matchReasons, matched keywords, and matched CPV codes
• Buyer, country, publication date, deadline, estimated value, and currency when available
• Direct links to the notice and published procurement documents
• Filters for keywords, exclusions, CPV codes, countries, notice stages, and dates
• Stable IDs, deduplication, and detection of new or materially changed notices
• Results ready for JSON, CSV, Excel, API, webhook, Make, Zapier, Slack, or other Apify integrations

The covered UK portal is Find a Tender. This Actor does not include Contracts Finder.

Quick start

Use a specific company profile and phrases that buyers are likely to use in a notice:

{
  "companyProfile": "We provide cloud platforms, custom software development, analytics dashboards, API integrations, and data migration services to public-sector organizations.",
  "keywords": [
    "cloud platform",
    "software development",
    "analytics dashboard",
    "API integration",
    "data migration"
  ],
  "excludeKeywords": ["hardware supply only", "construction work"],
  "cpvCodes": ["72000000"],
  "countries": ["DEU", "FRA", "IRL", "GBR"],
  "stages": ["competition"],
  "lookbackDays": 14,
  "minFitScore": 25,
  "onlyFutureDeadlines": true,
  "maxItems": 100,
  "mode": "search"
}

For a first run, start with a 7–14 day lookback, a few precise phrases, and the default minimum fit score of 25. Broad one-word keywords usually create more noise than product names, service phrases, or deliverables.

Public example

Run the published example from the Actor's Examples tab:

• Open the public example
• Open the Actor

The example is pre-filled with a realistic software-services search. You can run it as is, then duplicate it as your own Task and adjust the company profile, keywords, regions, or scoring threshold.

Pricing

The current offer is $5 per 1,000 tender matches, plus the small Actor-start charge shown in the Pricing tab. For example, a run that writes 200 matches costs about $1.00 in result events, plus the start charge. In monitor mode, unchanged notices that are not emitted do not incur a match charge.

Main inputs

Input	What it controls
companyProfile	A concrete description of your capabilities and deliverables. Required.
keywords	High-priority words or phrases used for discovery and ranking.
excludeKeywords	Drops notices containing unwanted words or phrases.
cpvCodes	Optional 2–8 digit CPV codes or category prefixes.
countries	Optional ISO alpha-3 country codes. Empty means all covered countries.
stages	Planning, open competition, result/award, or change notices.
lookbackDays	Moving date window used when exact dates are not supplied.
publishedFrom, publishedTo	Optional inclusive fixed date range.
minFitScore	Minimum relevance score required for output. Default: 25.
onlyFutureDeadlines	Excludes notices with a known expired deadline.
maxItems	Maximum number of ranked dataset items.
mode	search for current results or monitor for change tracking.

Choosing a fit threshold

• 15 — broad discovery, including weak or category-only signals
• 25 — balanced default for most searches
• 40+ — a smaller, more selective shortlist

The score is deterministic and based on the textual and classification evidence available in each notice. It is a prioritization aid, not a prediction of eligibility or win probability.

Search mode

Set mode to search to return the best current matches. Every result uses changeType: "search_result".

Search mode is best for:

• One-off opportunity research
• Building a tender dataset or CRM import
• Testing a new company profile or filter set
• Market and buyer research

Monitor mode

Set mode to monitor to remember matching notices between runs. Subsequent runs can emit only new or materially changed opportunities, so scheduled workflows remain quiet when nothing changed.

Recommended setup:

1. Create an Apify Task with mode: "monitor".
2. Give it a unique, stable monitorId.
3. Leave exact dates empty and use lookbackDays so the window moves automatically.
4. Choose baselineBehavior: "store_only" for a silent first run, or "emit" to receive the current backlog.
5. Add an Apify schedule and your preferred webhook or integration.

Leave emitUnchanged disabled for normal monitoring. A changed result includes changedFields, showing which material fields changed. Monitoring state is retained for up to 400 days and each monitor can track up to 25,000 procurements.

Output

Each dataset item is a normalized tender record. A typical result looks like this:

{
  "title": "Cloud platform and data migration services",
  "buyerName": "Example Contracting Authority",
  "countries": ["DEU"],
  "cpvCodes": ["72000000", "72260000"],
  "noticeStage": "competition",
  "publicationDate": "2026-08-20",
  "deadline": "2026-09-25T12:00:00+02:00",
  "estimatedValue": 1250000,
  "currency": "EUR",
  "fitScore": 58,
  "matchReasons": [
    "Title matches: cloud platform",
    "Description matches: data migration"
  ],
  "matchedKeywords": ["cloud platform", "data migration"],
  "matchedCpvCodes": ["72000000"],
  "changeType": "new",
  "changedFields": [],
  "url": "https://…"
}

The complete output also includes stable procurement and notice IDs, descriptions, procedure details, document links, value scope, and first/last-seen timestamps when available. Missing published values remain empty or null; values are not estimated or currency-converted.

Every run also writes RUN_SUMMARY, which reports the date range, processing counts, partial-coverage warnings, number of matches, number of emitted items, and monitor statistics.

Pricing and cost control

The Actor uses pay-per-result pricing. A tender match is charged only when it is written to the default dataset. In monitor mode, unchanged notices that are not emitted do not incur a result charge. A small Actor-start charge also applies.

Use maxItems, a focused date window, and Apify's maximum cost per run to keep spending predictable. See the Pricing tab for the current event prices.

Important behavior

• Exact dates override lookbackDays; the date range is inclusive.
• scanLimit must be at least maxItems and limits processing before final ranking.
• Broad CPV families improve coverage but may require supporting keyword evidence at the default score threshold.
• Country and value information can be absent or vary by notice.
• A successful run can legitimately return zero items when nothing meets your filters.
• If part of the coverage is temporarily unavailable, available matches may still be delivered and the warning will appear in RUN_SUMMARY.

Scope and limitations

This Actor discovers and monitors public procurement notice metadata. It does not log in to buyer portals, retrieve gated documents, prepare bids, determine legal eligibility, or make bid/no-bid decisions. Deadlines and requirements can change; review the linked notice and procurement documents before acting.

Fit scores are deterministic prioritization aids, not predictions of eligibility, win probability, or legal compliance. Always confirm the current deadline and requirements in the linked official notice.

Support

If a run behaves unexpectedly, open an issue from the Actor's Issues tab and attach the run URL. Include the expected outcome and the affected input or result so the problem can be reproduced quickly.