# DBA.dk Recommerce Listings Scraper (Denmark) (`stone_jadex/dba-dk-scraper`) Actor

Public DBA.dk recommerce forsale listings from search results: price (DKK), category, seller label, location, images, attributes, URL, and optional detail page. No start fee. Not Boligportal rentals.

- **URL**: https://apify.com/stone_jadex/dba-dk-scraper.md
- **Developed by:** [Stone Jade](https://apify.com/stone_jadex) (community)
- **Categories:** E-commerce
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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

## DBA.dk Listings Scraper

DBA.dk Listings Scraper gives Danish second-hand market researchers and resellers structured results from public pages. Start with a DBA search or item URL and export title, DKK price, location, category and public seller details.

### What you can do

- Compare published DKK asking prices for similar second-hand goods.
- Use location and category information to organize a local-market snapshot.
- Review seller type and item attributes when available to distinguish listings worth closer inspection.

### Who uses it

- A furniture reseller can compare chair prices and locations from a DBA search.
- A market analyst can collect bicycle listings and use detail descriptions to examine condition and specifications.

### Result preview

**Illustrative only:** invented examples show the shape of the data; they are not real results. A dash indicates an unavailable value.

| Title | Price | Location | Category | Seller type |
| --- | --- | --- | --- | --- |
| Used chair | 350 DKK | Example town | Furniture | Private |
| Used bicycle | 1,200 DKK | Example city | Bicycles | Private |
| Used table | 500 DKK | Example town | Furniture | — |

Fields may be absent when the source does not publish them.

### Why choose this Actor

- Start with a public search or an individual item page, depending on whether you are discovering or inspecting listings.
- Detail mode adds the full description, category path and richer attributes; a failed detail request can leave the list-level result.

### Pricing

Prices in **USD**, verified on 4 November 2026. Check the current Pricing tab before running.

| Result type | Event price |
| --- | ---: |
| List listing | $1.75 per 1,000 results |
| Listing with details | $1.75 per 1,000 results |

The detail event replaces the list event for the same result; the two are not added together. For example, 1,000 results at the list listing rate incur $1.75 in result-event charges. This calculation covers Actor event charges. Review Pricing for any separately listed platform usage; later access to stored data follows Apify's applicable storage pricing.

### Try it in three steps

1. Enter a DBA search or item URL. Set a small result limit for your first run.
2. Turn on **Open each listing page** for full descriptions and richer attributes, or leave it off for list results. Run the Actor.
3. Inspect the dataset and export the results in your preferred available format.

### Coverage and FAQ

**What are the limits?** A failed detail request can leave a list row. Published fields and the number of available listings vary.

The requested result limit defaults to 50 and can be set up to 2,000 per run.

**Is this a live feed?** Each run is a snapshot of available source information. Listings, prices and other details may change after collection; a requested maximum is a ceiling, not a promise of that many results.

**Can I use the data for ongoing analysis?** Yes, export it to your own workflow. Scheduling repeated runs or acting on the exported results requires your own workflow.

# Changelog

This Actor's version history is a separate document: https://apify.com/stone_jadex/dba-dk-scraper/changelog.md

# Actor input Schema

## `startUrls` (type: `array`):

Optional. A DBA.dk recommerce forsale search such as https://www.dba.dk/recommerce/forsale/search or https://www.dba.dk/recommerce/forsale/search?q=iphone, or an item URL /recommerce/forsale/item/{id}. Empty input uses forsale search + q=iphone. Mobility/car and Boligportal rentals are rejected.

## `maxItems` (type: `integer`):

Stop after this many listings.

## `maxPages` (type: `integer`):

Optional. Each search page has about 50–54 listings.

## `startPage` (type: `integer`):

First search page when the start URL does not already set ?page=.

## `scrapeDetails` (type: `boolean`):

Adds the full description, category path, and richer attributes from the item page. Charged as listing-detail instead of listing. Prefer list-only to stay within the cost gate. If a detail page fails, the list row is kept and charged as listing.

## `requestDelayMs` (type: `integer`):

At least 1 second between request starts (default 1.2 s). A Crawl-delay in robots.txt can only raise this.

## `concurrency` (type: `integer`):

How many search or detail pages may be requested at once. Rows are saved in page order. At least 1 second still passes between request starts.

## `maxRunSeconds` (type: `integer`):

Stops cleanly and writes the OUTPUT record before this limit.

## `proxyConfiguration` (type: `object`):

Direct connection by default. Do not default to residential. A residential proxy is a fallback only (turn on useProxyFallback) and is capped at a fixed 5 MB per run.

## `useProxyFallback` (type: `boolean`):

When a proxy is configured, stay on a direct connection until repeated HTTP 403 or 429 responses, then switch to that proxy. A residential proxy is meant to be used this way, as a fallback — never as the default.

## `allowDetailOnResidential` (type: `boolean`):

Detail pages stay on a direct connection when the proxy group is residential. Turn this on only if those detail pages should use the residential proxy too.

## Actor input object example

```json
{
  "maxItems": 50,
  "startPage": 1,
  "scrapeDetails": false,
  "requestDelayMs": 1200,
  "concurrency": 1,
  "maxRunSeconds": 3600,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "useProxyFallback": false,
  "allowDetailOnResidential": false
}
```

# Actor output Schema

## `listings` (type: `string`):

Public listing records saved in the default dataset, including an uncharged run-notice row when a run stops early.

## `summary` (type: `string`):

Crawl statistics, seed outcomes, errors, pricing events, and the stop reason saved under the OUTPUT key.

# 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("stone_jadex/dba-dk-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("stone_jadex/dba-dk-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 '{}' |
apify call stone_jadex/dba-dk-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,stone_jadex/dba-dk-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/IE2aaFaDdZKu0gojz/builds/WAGzcyVnj3vjOc1Ab/openapi.json