# Poland Public Tender Finder (e-Zamowienia/BZP, by CPV) (`chosen_loafer/procurement-monitor-actor`) Actor

Find open Polish public tenders matching your CPV codes on e-Zamowienia (BZP) before your competitors do, with deadline tracking. Can also run on a schedule as a daily new-tender monitor. No personal data is collected

- **URL**: https://apify.com/chosen_loafer/procurement-monitor-actor.md
- **Developed by:** [Pavel Staurouski](https://apify.com/chosen_loafer) (community)
- **Categories:** Lead generation, Automation, Business
- **Stats:** 2 total users, 1 monthly users, 76.5% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 tender checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Polish Public Procurement Monitor (e-Zamowienia / BZP by CPV code)

Monitors new Polish public tenders published on e-Zamowienia, filtered by CPV code and
publication date.

### What you get

One record per matching tender notice: notice number, title, CPV codes (main and
additional, across all lots), submission deadline, publication date, the contracting
authority's name, its current state, and a link to the official notice page. Nothing
about named individuals.

### What it does not do

No contact-person data, no attached documents (SWZ files), no full notice text beyond
what is needed to extract the CPV codes. Output is limited to structured tender metadata.

### Why you might need this

e-Zamowienia (and its BZP predecessor) publishes hundreds of tenders a day. Below-EU-
threshold Polish tenders (the majority by count) never reach TED, so a procurement
consultant or sales team watching a specific CPV category has no feed to subscribe to
beyond refreshing the portal's own search by hand.

### Input

A list of CPV codes to watch, and optionally a publication date window.

```json
{
  "cpvCodes": ["72000000"],
  "publishedFrom": "2026-10-01",
  "publishedTo": "2026-10-31",
  "maxResults": 100,
  "maxChecked": 300
}
```

`maxChecked` is a safety cap on how many candidate tenders get checked against your CPV
filter (each check is billed, whether or not it matches). It stops the run even if
`maxResults` matches haven't been found yet, e.g. for a narrow CPV filter with few
matches in the date window.

CPV matching uses hierarchy prefixes: a filter of `72000000` (IT services, division 72)
matches a notice tagged `72212000` (software development) and vice versa.

### Sample output

One record, run through this Actor's own field mapping against a representative
e-Zamowienia notice (dates in ISO 8601):

```json
{
  "noticeId": "2026/BZP 00474101/01",
  "title": "Dostawa sprzetu komputerowego",
  "cpvCodes": ["30213000", "48000000"],
  "deadline": "2026-10-20T12:00:00.000Z",
  "publicationDate": "2026-09-15T10:30:00.000Z",
  "publishingEntity": "Urzad Miasta Warszawy",
  "noticeType": "Initiated",
  "link": "https://ezamowienia.gov.pl/mo-client-board/bzp/notice-details/2026%2FBZP%2000474101%2F01"
}
```

### Pricing

Pay per run started, plus per tender notice checked against your CPV filter (not just
per match: checking is the real cost driver, since each candidate notice needs its own
request to read its CPV codes). See the Pricing tab for exact rates.

### Monitor przetargów publicznych (e-Zamówienia / BZP)

Monitoruje nowe polskie przetargi publiczne publikowane w systemie e-Zamówienia (BZP),
filtrowane według kodu CPV i daty publikacji.

Co otrzymujesz: jeden rekord na pasujące ogłoszenie, w tym numer ogłoszenia, tytuł, kody
CPV (główny i dodatkowe, ze wszystkich części zamówienia), termin składania ofert, datę
publikacji, nazwę zamawiającego, aktualny status postępowania oraz link do oficjalnego
ogłoszenia. Żadnych danych osobowych.

Dopasowanie kodów CPV działa hierarchicznie: filtr `72000000` (usługi IT) dopasuje też
ogłoszenie z kodem `72212000` (tworzenie oprogramowania) i odwrotnie.

Cennik: opłata za uruchomienie, plus opłata za każde sprawdzone ogłoszenie względem
filtra CPV, nie tylko za trafienie, ponieważ sprawdzenie każdego kandydata wymaga
osobnego zapytania o jego kody CPV.

# Actor input Schema

## `cpvCodes` (type: `array`):

List of CPV codes to monitor, e.g. \["72000000", "48000000"]. Matches against primary and additional CPV codes on the notice.

## `publishedFrom` (type: `string`):

ISO date (YYYY-MM-DD). Only notices published on or after this date are returned. Defaults to 30 days ago.

## `publishedTo` (type: `string`):

ISO date (YYYY-MM-DD). Only notices published on or before this date are returned. Defaults to today.

## `maxResults` (type: `integer`):

Maximum number of matching tender records to output.

## `maxChecked` (type: `integer`):

Safety cap on how many candidate tenders are checked against your CPV filter in this run (each check is a billed event, regardless of match). Stops the run even if "Max results" matches haven't been found yet, e.g. for a narrow CPV filter with few matches in the date window.

## Actor input object example

```json
{
  "cpvCodes": [
    "72000000"
  ],
  "maxResults": 100,
  "maxChecked": 300
}
```

# Actor output Schema

## `matchedTenders` (type: `string`):

Per-tender records.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "cpvCodes": [
        "72000000"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("chosen_loafer/procurement-monitor-actor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "cpvCodes": ["72000000"] }

# Run the Actor and wait for it to finish
run = client.actor("chosen_loafer/procurement-monitor-actor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "cpvCodes": [
    "72000000"
  ]
}' |
apify call chosen_loafer/procurement-monitor-actor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,chosen_loafer/procurement-monitor-actor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/JdaBMFd0tV3Qq8uzH/builds/HGL6D0nSSxLfjnLQi/openapi.json