DBA.dk Marketplace Scraper

Extract public marketplace listings from DBA.dk search and category pages. The actor collects Danish classified ads with prices, locations, images, item attributes, and optional detail-page descriptions.

What does DBA.dk Marketplace Scraper do?

DBA.dk Marketplace Scraper turns public DBA.dk marketplace pages into structured datasets. Provide one or more search queries such as iphone, sofa, or cykel, or paste DBA.dk marketplace URLs, and the actor returns listing rows that are ready for spreadsheets, BI dashboards, alerts, or pricing models.

Who is it for?

• 🛒 Resale teams tracking Danish second-hand prices.
• 📈 Ecommerce analysts monitoring local supply and demand.
• 🔔 Deal-alert builders watching specific keywords and locations.
• 🧾 Classifieds researchers collecting comparable listings.
• 🤖 Automation builders feeding DBA.dk data into enrichment workflows.

Why use this actor?

DBA.dk is one of Denmark's most important marketplace sources, but manual browsing is slow when you need repeatable data. This actor gives you clean records with stable listing URLs, numeric prices, images, location hints, and scrape timestamps so you can compare items over time.

How much does it cost to scrape DBA.dk listings?

This actor uses pay-per-event pricing. There is a small run-start event and a per-listing event. You only pay for records the actor saves to the dataset. Exact Store prices are shown on the Apify actor page and may include volume tiers for larger users.

Input options

Input	Description
queries	DBA.dk search keywords.
startUrls	DBA.dk search or category URLs.
maxItems	Maximum listings to save.
includeDetails	Visit detail pages for richer descriptions and images.
requestTimeoutSecs	Timeout per HTTP request.

Output data

Each dataset item represents one marketplace listing.

Field	Description
listingId	DBA.dk item ID parsed from the URL.
url	Public listing page.
title	Listing title.
price	Price text as displayed.
priceValue	Numeric price value.
currency	Usually DKK.
location	Location shown on the listing card.
postedAgo	Relative posting age when visible.
description	Detail or schema description when available.
attributes	Visible item attributes.
imageUrls	Listing image URLs.
isSponsored	Whether the card is marked as paid placement.
sourceUrl	Search/category page that produced the record.
scrapedAt	ISO timestamp for the scrape.

Example output

{
  "listingId": "22499066",
  "url": "https://www.dba.dk/recommerce/forsale/item/22499066",
  "title": "Apple iPhone 15 Pro Max 256 GB hvid",
  "price": "4.400 kr.",
  "priceValue": 4400,
  "currency": "DKK",
  "location": "Vallensbæk Strand",
  "postedAgo": "6 dage",
  "imageUrls": ["https://images.dbastatic.dk/dynamic/default/item/22499066/..."],
  "isSponsored": true,
  "sourceUrl": "https://www.dba.dk/recommerce/forsale/search?q=iphone",
  "scrapedAt": "2026-06-30T02:43:45.650Z"
}

How to scrape DBA.dk search results

1. Open the actor on Apify.
2. Enter one or more search queries, for example iphone or sofa.
3. Set maxItems to the number of listings you need.
4. Keep includeDetails disabled for faster monitoring runs, or enable it when descriptions matter.
5. Run the actor and export the dataset as JSON, CSV, Excel, or via API.

Search-query examples

• iphone
• sofa
• cykel
• kamera
• lego
• barnevogn

DBA.dk URL examples

Use URLs from the public marketplace area, for example:

https://www.dba.dk/recommerce/forsale/search?q=iphone
https://www.dba.dk/recommerce/forsale/search?q=sofa

Detail enrichment

When includeDetails is enabled, the actor opens every listing URL it is about to save. This can add richer descriptions and additional item images. Disable it when you only need fast search-card data or when you are running frequent monitors.

Tips for better results

• Start with a specific query and a small maxItems value.
• Use broad category/search URLs for market-size monitoring.
• Enable detail enrichment only for high-value workflows.
• Run the actor on a schedule to build a price-history table.
• Deduplicate externally by listingId if you merge multiple runs.

Integrations

• 📊 Send datasets to Google Sheets for daily price dashboards.
• 🔔 Trigger alerts when priceValue drops below your target.
• 🧠 Feed listing titles and descriptions into classification or enrichment models.
• 🗄️ Store records in a database keyed by listingId for trend analysis.
• 📨 Combine with Apify webhooks to notify a Slack channel after each run.

API usage: Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/dba-dk-marketplace-scraper').call({
  queries: ['iphone'],
  maxItems: 50,
});
console.log(run.defaultDatasetId);

API usage: Python

from apify_client import ApifyClient

client = ApifyClient('MY-APIFY-TOKEN')
run = client.actor('automation-lab/dba-dk-marketplace-scraper').call(run_input={
    'queries': ['sofa'],
    'maxItems': 50,
})
print(run['defaultDatasetId'])

API usage: cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~dba-dk-marketplace-scraper/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"queries":["iphone"],"maxItems":50}'

MCP usage

Use this actor from Claude Desktop, Claude Code, or other MCP-capable tools via Apify MCP Server:

https://mcp.apify.com/?tools=automation-lab/dba-dk-marketplace-scraper

Claude Code setup:

$claude mcp add apify-dba-dk --transport http "https://mcp.apify.com/?tools=automation-lab/dba-dk-marketplace-scraper"

Claude Desktop JSON configuration:

{
  "mcpServers": {
    "apify-dba-dk": {
      "url": "https://mcp.apify.com/?tools=automation-lab/dba-dk-marketplace-scraper"
    }
  }
}

Example prompts:

• "Scrape 50 DBA.dk listings for iPhone and summarize the price range."
• "Find recently posted sofa listings and return the cheapest five."
• "Monitor DBA.dk for camera listings and flag items below 1,000 DKK."

Scheduling and monitoring

Create an Apify schedule for daily or hourly checks. Use maxItems to control run size and cost. For recurring alerts, export only new listingId values since your previous run.

Data quality notes

DBA.dk page layout and visible fields can vary by category. Some listings include item attributes such as brand or storage size, while others only expose title, price, location, and images. Seller metadata is collected only when public markup exposes it.

Legality and responsible use

This actor extracts publicly available marketplace pages. Always use the data responsibly, respect DBA.dk terms, avoid excessive scraping, and do not collect or misuse private personal information.

FAQ

Is this a DBA.dk API?

No. The actor extracts public DBA.dk marketplace pages and returns structured data in an Apify dataset.

Troubleshooting

Why are some fields null?

DBA.dk does not expose every field on every listing. Enable includeDetails for richer records, but expect some seller or category fields to remain unavailable.

Why did my run return fewer records than expected?

The selected query may have fewer listings, DBA.dk may group sponsored cards differently, or maxItems may be lower than the number you expected. Try a broader query or URL.

Related scrapers

• DBA.dk Cars Scraper for vehicle-specific DBA.dk workflows.
• 2dehands / 2ememain Scraper for Belgian classifieds monitoring.
• 1688 Scraper for product sourcing workflows.

Changelog

• Initial version: public DBA.dk marketplace search/category scraping with optional detail enrichment.

Support

If your workflow needs an additional DBA.dk field or a category-specific extraction improvement, open an issue on the Apify actor page with an example URL.