Nordic Marketplace Scraper API - Blocket, FINN, DBA, Tori

vehicle

One car listing from Blocket, FINN or DBA with the full vehicle record, not just the ad text: make, model, series and trim, model year, mileage NORMALISED TO KILOMETRES (Blocket and FINN publish Scandinavian mil, where one mil is ten kilometres - a raw copy understates every Swedish and Norwegian car tenfold), fuel, transmission, registration class, the registration plate and the VIN where the marketplace publishes them, dealer name and trade-body memberships, and the price both including and excluding VAT where the seller states both. Priced above a plain classified row because it carries the vehicle identity fields a valuation or stock-monitoring workflow is actually built on. Billed once per car per run, and never billed for a row that could not be read.

company

One company from an official Nordic business register - Norway (Bronnoysundregistrene) or Finland (PRH/YTJ) - in one normalised schema: organisation number, current registered name (not a superseded historical one), legal form, industry code with its description, registered and incorporation dates, employee count where the register publishes it, full registered address with municipality, website, VAT registration, and the distress flags that lead-generation and credit workflows are built on: bankrupt and in-liquidation. Official open government data, so the row is authoritative rather than reconstructed from a directory page. Billed once per organisation number per run; with monitorChangesOnly on, only companies whose watched fields moved are billed.

job

One job advert from Platsbanken (Sweden, via the Arbetsformedlingen open API) or FINN (Norway), in one normalised schema: headline, employer with organisation number where published, occupation, employment and working-hours type, salary type, number of vacancies, application deadline as ISO 8601, publication date, the full workplace address with municipality, region and coordinates, and the direct application URL. Billed once per advert per run; a scheduled re-run with monitorChangesOnly on bills only adverts that are new or that changed, which is how a daily recruiting cron stays cheap.

listing-check

One ad that was actually fetched and compared but billed nothing, because you ran with monitorChangesOnly and it had not changed since your last run. A tenth of the price of the ad itself - you get the answer, not the listing. Charged once per ad per run, never on an ad that was delivered, and never on a page that was blocked or failed - those stay free. This is what keeps a price-watch schedule honest: a quiet day costs a tenth, and the day a price moves you are billed for the ad exactly as before.