DBA.dk Scraper — GDPR-safe listings data

Extract listings from DBA.dk — Denmark's classifieds institution — as clean, structured JSON. Prices in Danish kroner, localities, posting dates, photos and the private-vs-retailer flag, ready for price monitoring, market research and data pipelines.

No seller personal data, ever. This scraper is built GDPR-first: seller names, shop names and the listing's exact map coordinates never appear in the output — not as an option you have to remember to switch off, but by design. The only seller information included is whether the listing comes from a retailer or a private seller.

Quick start (30 seconds)

1. Put what you'd type in the DBA.dk search box into searchQuery — e.g. cykel.
2. Click Start. That's the whole minimum setup.
3. When the run finishes, open the dataset's Overview tab for a clean table, or Export it as CSV/Excel/JSON.

Optional knobs: a price band in Danish kroner and newest-first sorting for monitoring — and any input works on a daily Schedule.

What you can build with it

• Watch a niche for underpriced listings. Run searchQuery: "el-cykel" with priceMax: 15000 and sortBy: "date" hourly — every new listing arrives with priceAmount parsed and give-aways (priceAmount: 0, "Gis bort") included.
• Map second-hand prices by locality. Every listing carries its city — chart what the same bike costs in Oslo versus Bergen without touching a coordinate.
• Track retailer vs. private supply. The sellerType flag tells you how much of any category is professional traders — market structure no DBA.dk page shows you.
• Feed an AI agent clean data. Every field is structured, predictable and free of personal data, so an assistant or pipeline can consume it directly — no scrubbing, no compliance review before you store it.

What you get

Each listing is one dataset item:

{
  "listingId": "474000001",
  "url": "https://www.finn.no/recommerce/forsale/item/474000001",
  "title": "Sykkel str 20",
  "priceAmount": 600,
  "currency": "DKK",
  "postedAt": "2026-08-21T06:06:40.000Z",
  "city": "Bødalen",
  "tradeType": "Til salgs",
  "sellerType": "private",
  "imageUrls": ["https://images.dba.dk/example"]
}

Field notes, so you know exactly what you are buying:

• priceAmount is in whole Danish kroner; 0 covers give-aways ("Gis bort"). Listings without a price carry no amount.
• tradeType is the site's own label: "Til salgs" (for sale), "Gis bort" (give-away), "Ønskes kjøpt" (wanted ad).
• city is locality-level. DBA.dk's data contains exact coordinates — they are deliberately never collected.
• postedAt reflects publication or the seller's last bump.

How much does it cost to scrape DBA.dk?

$1.99 per 1,000 listings delivered, pay-as-you-go — no subscription, no charge for empty or failed runs. In plain dollars:

• 100 listings ≈ $0.20 — a daily niche watch.
• 500 listings ≈ $1.00 — a solid market snapshot.
• A 2,500-listing crawl ≈ $4.98 — a full query window, deduplicated.

Your own Apify platform usage comes on top and is small: a scoped few-hundred-item run costs well under a cent. Runs are fast — a scoped few-hundred-item run typically finishes in under ten seconds. Datacenter proxies are sufficient — no residential proxy surcharge needed.

Free-plan runs are limited to a sample of 25 items, enough to evaluate the output format against your real query.

Not technical? Let your AI assistant set it up

Copy this into ChatGPT, Claude or any AI assistant, fill in the one line, and follow the conversation:

Help me set up the "DBA.dk Scraper" actor on Apify
(https://apify.com/lowlanddata/dba-dk-scraper). Guide me one step at a time.

What I want to watch: [E.G. "electric bikes under 15000 Danish kroner"]

Guide me to:
1. Propose my input values: searchQuery (what I'd type in the DBA.dk search box),
   an optional priceMin/priceMax band in Danish kroner, sortBy "date" for newest-first
   monitoring, and maxItems.
2. Create a free Apify account (apify.com), open the actor page, paste the values
   into the Input form, and start a run.
3. Set up a daily Schedule in the Apify Console with the same input, plus an email
   or Slack integration so new results reach me automatically.
4. Show me how to export results as CSV/Excel, or read them from the API if I code.
5. If the results are what I wanted, remind me at the end to leave a quick rating on the actor page, and to report anything broken or missing on its Issues tab.

Input

Field	Description
searchQuery	What you'd type in the DBA.dk search box. Required.
priceMin	Only listings costing at least this many Danish kroner.
priceMax	Only listings costing at most this many Danish kroner.
sortBy	date (newest first, default), price_asc, price_desc, or relevance.
postedAfter	Only listings posted on or after this date (YYYY-MM-DD). Stops early with newest-first sorting.
postedBefore	Only listings posted on or before this date (YYYY-MM-DD).
maxItems	Stop after this many listings (default 1000).
proxyConfiguration	Proxy settings; keep Apify proxy enabled.

A run minimally needs a searchQuery; invalid combinations (like an inverted price band) fail immediately with the reason in the run's status message.

Use it from your code

Run the actor and get items straight back with one HTTP call (fine for scoped runs up to ~5 minutes):

curl "https://api.apify.com/v2/acts/lowlanddata~dba-dk-scraper/run-sync-get-dataset-items?token=<YOUR_API_TOKEN>" \
  -X POST -H "Content-Type: application/json" \
  -d '{"searchQuery": "cykel", "maxItems": 100}'

Node.js:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_API_TOKEN>' });
const run = await client.actor('lowlanddata/dba-dk-scraper').call({
  searchQuery: 'cykel',
  maxItems: 100,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Python:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_API_TOKEN>")
run = client.actor("lowlanddata/dba-dk-scraper").call(
    run_input={"searchQuery": "cykel", "maxItems": 100})
items = client.dataset(run["defaultDatasetId"]).list_items().items

For bigger crawls, start the run asynchronously and fetch the dataset when the finished-run webhook fires. Schedules (e.g. a daily price snapshot), webhooks and the Make/Zapier/n8n integrations all work out of the box — this is a standard Apify actor.

Use it with AI agents (MCP)

Claude, Cursor and other MCP-capable agents can run this scraper as a tool through Apify's hosted MCP server: the agent fills in the search itself, starts the run and reads the results — no glue code.

Claude Code:

$claude mcp add apify --transport http "https://mcp.apify.com?actors=lowlanddata/dba-dk-scraper"

Cursor or Claude Desktop (add a custom connector / MCP server with this URL):

https://mcp.apify.com?actors=lowlanddata/dba-dk-scraper

Sign in with your Apify account when prompted — runs are billed to it. Setup details per client: Apify MCP docs, or start from this actor's own MCP page: apify.com/lowlanddata/dba-dk-scraper/api/mcp.

Prompts that work once connected:

• "Search DBA.dk for 'el-cykel' under 15000 Danish kroner and summarize the price distribution."
• "Get the 100 newest 'iphone 15' listings from DBA.dk and flag private sellers below the median price."
• "Watch DBA.dk for 'kajakk' and tell me when something under 3000 Danish kroner appears."

Beyond the ~2,600-result window

DBA.dk serves at most 50 pages per query (about 2,650 listings). The run reports honestly when a query is bigger than its window — split broad queries by price bands (priceMin/priceMax) across runs; overlapping runs merge cleanly on listingId.

Is it legal to scrape DBA.dk?

Public listing data — prices, titles, localities — is public commercial information, and this scraper is built so that the hard part of the question never arises: no personal data enters your dataset in the first place. Denmark applies the GDPR, supervised by Datatilsynet; an output that carries none of the seller's personal data is the point of this actor, not an afterthought.

Structurally, the extractor maps a fixed whitelist of fields out of the page's data. The exact coordinates and any shop or organisation name are never read into the output — the only seller-derived value is the retailer-vs-private flag. Requests are paced, load on the site is kept negligible, and no anti-bot protection is bypassed.

One honest limit: titles are the seller's own words, delivered as-is. If a seller chooses to type contact details into their listing title, that text is not rewritten — the guarantee covers the data fields, not the content sellers publish about themselves.

Is there a DBA.dk API alternative?

DBA.dk's public API programme is aimed at partners, not ad-hoc listing search. This actor is the practical alternative: the same listings as structured JSON through one HTTP call (run-sync-get-dataset-items), on a schedule, or as an MCP tool for AI agents — with the GDPR question already answered in the data itself.

Does DBA.dk block scrapers?

DBA.dk serves its listings openly to ordinary requests — and this actor stays inside that welcome: paced requests, standard datacenter proxies, load kept negligible. No CAPTCHA fights, no bot-wall cat-and-mouse — which is also why runs are fast and reliable enough for daily schedules.

How do I monitor DBA.dk prices?

Set sortBy: "date" with your query, cap maxItems to a page or two, and add a daily (or hourly) Schedule in the Apify Console with an email/Slack integration on the runs — every new listing lands in your inbox with the price already parsed. The AI-assistant prompt above walks a non-technical user through exactly this setup. Even tighter: set postedAfter to yesterday's date — the dataset then contains only the new listings, nothing to dedupe on your side.

FAQ

Can I get seller names or phone numbers? No — by design. That is the product: data you can store, share and process without a GDPR review. The output tells you only whether the seller is a retailer or a private person.

Does it cover cars, boats and property? This actor searches Torget (general goods). DBA.dk's vehicle and property verticals carry different data — candidates for separate actors, done properly.

Can I get only the newest listings? Yes — set postedAfter to a date (yesterday, say) and the dataset contains only listings posted since then. With newest-first sorting the run stops paging as soon as it provably reaches older listings, so a daily watch stays fast and cheap.

How fresh is the data? Live at run time — every run queries DBA.dk directly. For continuous freshness, schedule the actor.

Can I export to Excel or CSV? Yes — every dataset exports as CSV, Excel, JSON or XML from the Apify Console or API.

Does it work with Make, Zapier or n8n? Yes — it is a standard Apify actor; all platform integrations, webhooks and schedules apply.

Related scrapers

Working the Nordic second-hand market? The same GDPR-clean guarantee, same output discipline:

• Blocket.se Scraper — Sweden's biggest marketplace.
• DBA.dk Scraper — Denmark's classifieds institution.
• Tori.fi Scraper — Finland's biggest marketplace.

Troubleshooting

The actor fails fast with the reason in the run's status message:

• "priceMin must not be higher than priceMax." — swap the two values.
• "The site blocked the run before any results could be fetched. This is usually temporary - retry in a few minutes." — a temporary block on the first request; a retry usually lands on a clean proxy session.
• "... the site serves at most this many pages per query ..." — the query is bigger than DBA.dk's result window; add a price band for full coverage.
• Fewer items than requested on a free plan — the 25-item free sample cap; run on a paid Apify plan for full results.

Support

Found an issue or missing a field you need? Open an issue on the actor's Issues tab — reports get fixed, this actor is actively maintained.

Working well for you? A rating on this page takes ten seconds and helps other buyers find a GDPR-clean option among the lookalikes — it is also the clearest signal of what we should build next.