# Polish e-Zamowienia Public Bids Scraper (`dataforge_api/pl-ezamowienia-public-bids-ppe`) Actor

Polish public procurement (official e-Zamowienia BZP API): award results with winning contractors and tax IDs, tenders with buyer address, email and website. Filter by CPV, keyword, buyer, date. Pay-per-event.

- **URL**: https://apify.com/dataforge_api/pl-ezamowienia-public-bids-ppe.md
- **Developed by:** [DataForge Lab](https://apify.com/dataforge_api) (community)
- **Categories:** Business, Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 polish procurement notices

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 e-Zamowienia Public Bids

Poland's public procurement notices from the official e-Zamowienia BZP API (open, no key): who bought what, who won, and how to reach the buyer. Filter by CPV code, keyword, buyer and date.

### Who uses it

- **Suppliers and contractors** looking for Polish tenders in their category (construction, medical equipment, machinery, IT).
- **Sales teams** building lists of companies that recently won public contracts (winners are listed on award notices with tax ID and address).
- **Market analysts** tracking public spending by buyer, region or CPV.

### Input

```json
{
  "noticeTypes": ["TenderResultNotice"],
  "cpvPrefixes": ["45", "33"],
  "keywords": [],
  "buyerName": "",
  "lastDays": 3,
  "maxResults": 50
}
```

- `noticeTypes`: `TenderResultNotice` (award result, lists the winning contractors), `ContractNotice` (open tender) and other BZP types.
- `cpvPrefixes`: CPV codes or prefixes, e.g. 45 construction, 33 medical, 42 machinery.
- `keywords`: Polish or English words that must appear in the title.
- `buyerName`: part of the contracting authority name.
- `lastDays`, `publishedFrom`, `publishedTo`: date range, newest day first.
- `maxResults`: cap on saved notices.

### Output per notice

`notice_number`, `bzp_number`, `notice_type`, `order_type`, `title`, `publication_date`, `offers_deadline`, `procedure_result`, `cpv_codes`, buyer name, city, tax ID, street, postal code, email, website, `contractors` (winning company name, address, province, tax ID), `notice_url`.

### Honest limits

- Texts are in Polish as published.
- `contractors` is filled only on award result notices.
- Buyer email, website and street are read from the published notice text when present; phone numbers are rarely published.
- Only what the official API returns is available; nothing is scraped behind a login.

### Pricing

Pay per event: `pl-ezamowienia-public-bids-record` $0.004 per saved notice.

# Actor input Schema

## `noticeTypes` (type: `array`):

BZP notice types: TenderResultNotice (award result, lists the winning contractors), ContractNotice (open tender), PreInformationNotice, NoticeUpdateNotice, ContractPerformingNotice.

## `cpvPrefixes` (type: `array`):

Optional. CPV codes or prefixes, e.g. 45 (construction), 33 (medical equipment), 42 (machinery). Each one is searched separately.

## `keywords` (type: `array`):

Optional. Polish or English words that must appear in the notice title.

## `buyerName` (type: `string`):

Optional. Part of the contracting authority name.

## `lastDays` (type: `integer`):

Used when Published from is empty. Newest day first.

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

Optional. Earliest publication date, format YYYY-MM-DD.

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

Optional. Latest publication date, format YYYY-MM-DD. Defaults to today.

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

Maximum number of notices to save.

## Actor input object example

```json
{
  "noticeTypes": [
    "TenderResultNotice"
  ],
  "cpvPrefixes": [],
  "keywords": [],
  "lastDays": 3,
  "maxResults": 50
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `dataset` (type: `string`):

No description

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("dataforge_api/pl-ezamowienia-public-bids-ppe").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("dataforge_api/pl-ezamowienia-public-bids-ppe").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 '{}' |
apify call dataforge_api/pl-ezamowienia-public-bids-ppe --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dataforge_api/pl-ezamowienia-public-bids-ppe"
        }
    }
}
```

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/g8QUvzUNu5XAUvWWn/builds/6kv6le1IedRnL2ju9/openapi.json
