# Udbud Tender Scraper (`scrapingmonkey/udbud-tender-scraper`) Actor

Scrape Udbud procurement notices. Search public records. Export available fields to Excel, CSV or JSON.

- **URL**: https://apify.com/scrapingmonkey/udbud-tender-scraper.md
- **Developed by:** [ScrapingMonkey](https://apify.com/scrapingmonkey) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

Extract Udbud procurement notices for tender discovery, buyer research and procurement monitoring. **Udbud Tender Scraper** collects public information into one complete dataset table, ready to export as Excel, CSV or JSON.

Use search filters, set how many results you need and start the Actor. Search returns the fields made available in this service’s public results.

| At a glance | Details |
|---|---|
| 📥 Input | Search filters |
| 📋 Collection modes | Search tender records |
| 📤 Output | One row per record, or a failed row for an unsuccessful input |
| 📄 Pagination | Automatic, up to `maxResults` while more records are available |
| 🔐 Website login | Not required |
| 💾 Export | One dataset view with all fields; Excel, CSV and JSON |

### What the Udbud scraper collects 📋

| Mode | What you receive |
|---|---|
| **Search tender records** | Matching procurement notices and the fields published in the search results. |

The field table and complete examples below show the information this Actor returns. Optional values depend on what the source publishes for the selected record.

Coverage for this Actor:

- Returns public search records in Danish and English where available. A separate notice details mode is not provided.

### How to scrape Udbud 🚀

1. Choose **Search tender records**.
2. Complete the search filters.
3. Set **Maximum results**. The minimum is 1.
4. Start the Actor and review the saved dataset.
5. Export the results or connect them to your workflow.

#### Search tender records — input example

```json
{
  "mode": "search",
  "maxResults": 10
}
```

`maxResults` limits all saved rows for each search or supplied record, including a failed row. It does not guarantee that the source has that many matching records.

### Udbud data fields and complete output 📦

Each result stays in one row. Every returned field appears in the same dataset view, including list fields and additional published facts. Fields unavailable for a particular record remain empty.

| Field | Included data |
|---|---|
| `result_type` | Selected collection mode. |
| `input` | Submitted search settings, record link or record number. |
| `status` | Success or failed outcome. |
| `error_code` | Failure category for an unsuccessful input. |
| `error_message` | Readable explanation for an unsuccessful input. |
| `data_da.titel` | Data da / titel, when published. |
| `data_da.ordregiver` | Data da / ordregiver, when published. |
| `data_da.ordregiver_id` | Data da / ordregiver id, when published. |
| `data_da.ordregiver_id_datavasket` | Data da / ordregiver id datavasket, when published. |
| `data_da.publiceringsdato` | Data da / publiceringsdato, when published. |
| `data_da.cpv_kode` | Data da / cpv kode, when published. |
| `data_da.cpv_titel` | Data da / cpv titel, when published. |
| `data_da.formulartype` | Data da / formulartype, when published. |
| `data_da.formulartype_kode` | Data da / formulartype kode, when published. |
| `data_da.tidsfrister` | Data da / tidsfrister, when published. |
| `data_da.alle_ordregivere` | Data da / alle ordregivere, when published. |
| `data_da.forventet_opstart` | Data da / forventet opstart, when published. |
| `data_da.anslaaet_vaerdi` | Data da / anslaaet vaerdi, when published. |
| `data_da.anslaaet_vaerdi_valuta` | Data da / anslaaet vaerdi valuta, when published. |
| `data_da.beskrivelse` | Data da / beskrivelse, when published. |
| `data_da.bk_sub_type_kode` | Data da / bk sub type kode, when published. |
| `data_da.bk_sub_type` | Data da / bk sub type, when published. |
| `data_da.er_aendring` | Data da / er aendring, when published. |
| `data_en.titel` | Data en / titel, when published. |
| `data_en.ordregiver` | Data en / ordregiver, when published. |
| `data_en.ordregiver_id` | Data en / ordregiver id, when published. |
| `data_en.ordregiver_id_datavasket` | Data en / ordregiver id datavasket, when published. |
| `data_en.publiceringsdato` | Data en / publiceringsdato, when published. |
| `data_en.cpv_kode` | Data en / cpv kode, when published. |
| `data_en.cpv_titel` | Data en / cpv titel, when published. |
| `data_en.formulartype` | Data en / formulartype, when published. |
| `data_en.formulartype_kode` | Data en / formulartype kode, when published. |
| `data_en.tidsfrister` | Data en / tidsfrister, when published. |
| `data_en.alle_ordregivere` | Data en / alle ordregivere, when published. |
| `data_en.forventet_opstart` | Data en / forventet opstart, when published. |
| `data_en.anslaaet_vaerdi` | Data en / anslaaet vaerdi, when published. |
| `data_en.anslaaet_vaerdi_valuta` | Data en / anslaaet vaerdi valuta, when published. |
| `data_en.beskrivelse` | Data en / beskrivelse, when published. |
| `data_en.bk_sub_type_kode` | Data en / bk sub type kode, when published. |
| `data_en.bk_sub_type` | Data en / bk sub type, when published. |
| `data_en.er_aendring` | Data en / er aendring, when published. |
| `notice_id` | Notice id, when published. |
| `notice_version` | Notice version, when published. |
| `notice_publication_number` | Notice publication number, when published. |
| `record_id` | Stable identifier for the source record. |
| `url` | Public source link when the website provides one. |
| `additional_fields.name` | Names of additional published fields, when present. |
| `additional_fields.value` | Their corresponding values in the same order. |

The complete result below is included for every mode. Text and lists are not shortened. These are examples from validation runs; the source can change.

#### Search tender records — complete JSON result

```json
{
  "result_type": "search",
  "input": "{\"keywords\": null, \"noticeStatus\": \"AKTIV\"}",
  "data_da.titel": "Udbud af 11 delaftaler (rammeaftaler) vedrørende test, instruktion og studiestøttetimer på videregående uddannelser",
  "data_da.ordregiver": "Styrelsen for Undervisning og Kvalitet",
  "data_da.ordregiver_id": "ORG-2963 4750",
  "data_da.ordregiver_id_datavasket": "29634750",
  "data_da.publiceringsdato": "29-09-2026",
  "data_da.cpv_kode": "85000000",
  "data_da.cpv_titel": "Sundhedsvæsen og sociale foranstaltninger",
  "data_da.formulartype": "Forventet indkøb",
  "data_da.formulartype_kode": "preplanning",
  "data_da.tidsfrister": [],
  "data_da.alle_ordregivere": [
    "Styrelsen for Undervisning og Kvalitet"
  ],
  "data_da.forventet_opstart": "Oktober 2026",
  "data_da.anslaaet_vaerdi": "250000000",
  "data_da.anslaaet_vaerdi_valuta": "DKK",
  "data_da.beskrivelse": "Forventet udbud af 11 delaftaler (rammeaftaler) vedrørende levering af test, instruktion og studiestøttetimer til studerende med ordblindhed på videregående uddannelser. Rammeaftalen vil omfatte levering af følgende ydelser: \n• Test af ordblindhed\n• Instruktion i læse-skriveteknologi\n• Studiestøttetimer\nRammeaftalen vil være opdelt i 11 delaftaler, hvoraf hver delaftale indgås med én leverandør. Delaftale 1-5 vedrører korte og mellemlange videregående uddannelser. Delaftale 7-10 vedrører lange videregående uddannelser. Delaftale 11 er Bornholms Regionskommune, hvor både korte, mellemlange og lange videregående uddannelser er omfattet. Her fremgår en liste over delaftalerne:\n• Delaftale 1: Region Hovedstaden\n• Delaftale 2: Region Sjælland\n• Delaftale 3: Region Syddanmark\n• Delaftale 4: Region Midtjylland \n• Delaftale 5: Region Nordjylland \n• Delaftale 6: Region Hovedstaden\n• Delaftale 7: Region Sjælland\n• Delaftale 8: Region Syddanmark\n• Delaftale 9: Region Midtjylland\n• Delaftale 10: Region Nordjylland\n• Delaftale 11: Bornholms Regionskommune\n\nMålgruppen for rammeaftalen er ordblinde studerende på videregående uddannelser, der bevilges specialpædagogisk støtte (støttemodtagere).",
  "data_da.bk_sub_type_kode": "DKE0",
  "data_da.bk_sub_type": "Forventet indkøb",
  "data_da.er_aendring": true,
  "data_en.titel": "Udbud af 11 delaftaler (rammeaftaler) vedrørende test, instruktion og studiestøttetimer på videregående uddannelser",
  "data_en.ordregiver": "Styrelsen for Undervisning og Kvalitet",
  "data_en.ordregiver_id": "ORG-2963 4750",
  "data_en.ordregiver_id_datavasket": "29634750",
  "data_en.publiceringsdato": "29-09-2026",
  "data_en.cpv_kode": "85000000",
  "data_en.cpv_titel": "Health and social work services",
  "data_en.formulartype": "Anticipated procurement",
  "data_en.formulartype_kode": "preplanning",
  "data_en.tidsfrister": [],
  "data_en.alle_ordregivere": [
    "Styrelsen for Undervisning og Kvalitet"
  ],
  "data_en.forventet_opstart": "October 2026",
  "data_en.anslaaet_vaerdi": "250000000",
  "data_en.anslaaet_vaerdi_valuta": "DKK",
  "data_en.beskrivelse": "Forventet udbud af 11 delaftaler (rammeaftaler) vedrørende levering af test, instruktion og studiestøttetimer til studerende med ordblindhed på videregående uddannelser. Rammeaftalen vil omfatte levering af følgende ydelser: \n• Test af ordblindhed\n• Instruktion i læse-skriveteknologi\n• Studiestøttetimer\nRammeaftalen vil være opdelt i 11 delaftaler, hvoraf hver delaftale indgås med én leverandør. Delaftale 1-5 vedrører korte og mellemlange videregående uddannelser. Delaftale 7-10 vedrører lange videregående uddannelser. Delaftale 11 er Bornholms Regionskommune, hvor både korte, mellemlange og lange videregående uddannelser er omfattet. Her fremgår en liste over delaftalerne:\n• Delaftale 1: Region Hovedstaden\n• Delaftale 2: Region Sjælland\n• Delaftale 3: Region Syddanmark\n• Delaftale 4: Region Midtjylland \n• Delaftale 5: Region Nordjylland \n• Delaftale 6: Region Hovedstaden\n• Delaftale 7: Region Sjælland\n• Delaftale 8: Region Syddanmark\n• Delaftale 9: Region Midtjylland\n• Delaftale 10: Region Nordjylland\n• Delaftale 11: Bornholms Regionskommune\n\nMålgruppen for rammeaftalen er ordblinde studerende på videregående uddannelser, der bevilges specialpædagogisk støtte (støttemodtagere).",
  "data_en.bk_sub_type_kode": "DKE0",
  "data_en.bk_sub_type": "Anticipated procurement",
  "data_en.er_aendring": true,
  "notice_id": "fc708037-3cac-445d-a74d-acb64eedc0dc",
  "notice_version": "01",
  "notice_publication_number": "",
  "status": "success",
  "record_id": "fc708037-3cac-445d-a74d-acb64eedc0dc:01",
  "url": null,
  "additional_fields.name": [],
  "additional_fields.value": []
}
```

### Input settings ⚙️

| Setting | What to enter |
|---|---|
| **What to collect** (`mode`) | Choose the information you need. |
| **Maximum results per search or link** (`maxResults`) | Collect up to this many saved results for each search or record link. Minimum: 1. |
| **Keywords** (`keywords`) | Words to search for in public tender records. Leave empty to browse all available results. |
| **Notice status** (`noticeStatus`) | Choose current notices or all notices. |

### Udbud scraping use cases 🎯

#### Build a tender or contract shortlist

Search the supported procurement collection and export matching records. Keep deadlines, buyer names and original references together when reviewing opportunities.

#### Research public buyers

Compare available buyer, supplier and contract information across records. Preserve the published currency and value type when working with amounts.

#### Monitor published procurement records

Schedule repeated exports and compare stable record IDs to identify newly published notices and changes. A search result is not confirmation that bidding remains open.

### Pricing and saved-result behavior 💰

See the Actor’s **Pricing** tab for the current rate. Under dataset-item pricing:

- Each saved record is one result. Lists and additional details attached to it do not create extra rows.
- A saved `failed` row is also one billable dataset item. This includes invalid inputs, unavailable records, empty searches and exhausted retries.
- At most one failed row is saved per input. Retry attempts do not create additional dataset rows.
- `maxResults` caps all saved rows for the input. Duplicate copies of the same input are processed once.

### Udbud scraper API and integrations 🔌

Replace `$ACTOR_ID` with the ID shown in the Actor’s API tab and `$APIFY_TOKEN` with your Apify token.

```bash
curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"search","maxResults":10}'
```

Use Apify schedules for recurring collection, webhooks for completion notifications, and integrations for Google Sheets, Make, Zapier, cloud storage or your own application.

### Reliability and public-data limits ⚠️

Temporary request failures are retried up to five total attempts. Invalid record inputs save a failed row without a website request. Confirmed missing records are not retried unnecessarily. If a later request fails, records already saved remain in the dataset. Normal pagination completion does not add a failed row. Collection stops after two consecutive pages return no new records. Configuration, data-saving or request-scheduling failures stop the run.

Udbud controls the available records and fields. Search records can contain less information than a full public card. The Actor preserves published values and does not fill missing facts with estimates.

### Frequently asked questions ❓

#### Do I need a Udbud account?

No. This Actor collects the supported public information without your website login.

#### Which search filters can I use?

The input form supports keywords, notice status. Only the displayed filters are supported.

#### How many records can I collect?

Set `maxResults` to the maximum saved rows you want for each input. The minimum is 1. Collection can finish earlier when the source runs out of results or stops returning new records.

#### Why are some fields empty?

The source may not publish a value for that record or mode. Optional information remains empty.

#### Can I export all the fields?

Yes. All returned fields are included in one dataset view. Nested lists remain attached to their parent record.

### Support 🛟

For a reproducible issue, share the run ID, selected mode and a safe public example through the Actor’s support channel. Keep tokens, passwords and proxy credentials private.

# Actor input Schema

## `mode` (type: `string`):

Choose the information you need.

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

Collect up to this many saved results for each search or record link. Minimum: 1.

## `keywords` (type: `string`):

Words to search for in public tender records. Leave empty to browse all available results.

## `noticeStatus` (type: `string`):

Choose current notices or all notices.

## Actor input object example

```json
{
  "mode": "search",
  "maxResults": 10,
  "noticeStatus": "AKTIV"
}
```

# Actor output Schema

## `results` (type: `string`):

Results and failed input outcomes, with all returned fields.

# 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 = {
    "mode": "search",
    "maxResults": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapingmonkey/udbud-tender-scraper").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 = {
    "mode": "search",
    "maxResults": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("scrapingmonkey/udbud-tender-scraper").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 '{
  "mode": "search",
  "maxResults": 10
}' |
apify call scrapingmonkey/udbud-tender-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapingmonkey/udbud-tender-scraper"
        }
    }
}
```

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/K0eIzKnsIJfXrIqtY/builds/QnqPOSsFIpOrFVecn/openapi.json