Blocket Scraper: Sweden New Listing Alerts

Watch a search, get only what's new. This actor runs your search against Blocket.se's own search-results pages — Sweden's largest classifieds marketplace — and returns one clean row per listing: title, price, condition, brand, and a permanent link. Turn on monitoring and it becomes a watchlist: new listings and price drops since your last run, charged per new row, free on quiet days. Turn on "Alert on gone listings" and it is also a Blocket sold items tracker: listings that disappeared since the last run (most often sold), a presumed-sold flag, days listed, and a lifetime sell-through rate and median price for the search. Schedule it hourly and send the results to Discord, Slack, Google Sheets, or n8n.

Who it's for

A reseller or arbitrage buyer watching one category (phones, bikes, electronics) for underpriced or newly-posted listings wants a live feed of what's actually on Blocket right now, without refreshing the search page by hand or babysitting Blocket's own "bevakning" (saved-search) alerts inside its app. A market-research team tracking asking prices for a product category, or a Sheets/n8n workflow that reacts the moment something new is posted, gets the same shape here: paste a list of search terms, get back a flat row per listing, and pay only for listings actually returned — a search that finds nothing costs nothing.

This actor is Blocket's member of the same Nordic classifieds family as dba-listing-lookup (Denmark) in this catalogue — Blocket, DBA, Finn.no, and Tori.fi all run on the same Schibsted/Vend "recommerce" platform, so the same search shape and monitoring model work the same way on each.

Why this one

• Monitoring first, not a one-off dump. Turn on "Only return results that are new, or dropped in price" and this actor becomes a watchlist: it remembers every listing ID it has already shown you, and only bills you for what's actually new or has dropped in price since the last run. A quiet run — nothing new, nothing cheaper — still finishes and costs only the base run fee.
• A sold signal, not just new listings. With "Alert on gone listings" on, a watchlist also reports listings that left Blocket since the last run, flags the ones presumed sold, and keeps a lifetime sell-through rate for the search. Gone rows are ordinary listing rows: no extra event, no extra request. See "Sold signal and sell-through" below.
• Reads Blocket's own structured listing data. Every base field comes from the seoStructuredData JSON-LD block Blocket's own pages embed for search engines — not text scraped from rendered HTML — so price, currency, condition, and brand are exact, typed values.
• Never charged for a miss, or a quiet monitoring run. A search that finds nothing, or a scheduled watchlist run where nothing changed, still gets a row explaining what happened — and costs nothing. See "Pricing" below for the found-row rate.
• Honest about what Blocket doesn't expose statically. Blocket's search and item pages don't serve a posted-time or seller identity anywhere in the static response (confirmed directly, not assumed) — this actor doesn't fabricate those fields. See "Data & privacy" and the FAQ for what that means and what you do get from the optional details hop.
• Paste a keyword or your own saved search URL. Type plain keywords, or paste a Blocket search-results URL you've already filtered on the site — its filters carry straight through.

What you get

One row per listing by default (turn off "Expand rows" in Advanced to get one row per search instead, with the listings nested under listings).

Field	Type	Description
query	text	The search you submitted, echoed back
found	boolean	true if Blocket returned a real search-results page for this search
status	text	OK on a match; NOT_FOUND, BLOCKED, or BAD_FORMAT on a miss
message	text	Plain-English reason for a miss — only present when found is false
searchQuery	text	The keyword actually searched (parsed out of a pasted URL, if you gave one)
listingCount	number	Listings returned and billed for this search
totalAvailable	number	Total listings Blocket reports matching this search, including ones not returned
truncated	boolean	true if more results existed than were returned
newCount	number	New listings this run (monitoring only)
priceDropCount	number	Price drops this run (monitoring only)
detailsCount	number	Listings this run fetched the item-page details for
monitorStatus	text	NO_NEW_ROWS on a quiet monitoring run, WATCHLIST_SEEDED on a silent first run, otherwise empty
goneCount	number	Listings detected as gone this run, returned or not (monitoring only)
sellThroughRate	number	Lifetime share of this watchlist's tracked listings that went gone, 0 to 1 (monitoring only)
medianPrice	number	Median SEK price of everything this run fetched for the search, not only the rows returned (monitoring only)
listingId	text	Blocket's own numeric listing ID
title	text	Listing title
price	number	Price in SEK, or empty if the listing has no price
currency	text	Always SEK
condition	text	New, Used, Refurbished, or Damaged, as Blocket labels it
brand	text	Brand, when Blocket's listing has one
imageUrl	text (link)	First listing image
description	text	The listing's blurb; upgraded to the full (contact-info-redacted) description when details are fetched
city	text	Details only. The seller's city
category	text	Details only. Full Blocket category path
changeType	text	new, price-drop, gone, or seen (monitoring only)
isNew	boolean	true on this listing's first appearance (monitoring only)
previousPrice	number	The price last recorded for this listing, when it dropped (monitoring only)
priceDropPct	number	Percentage drop from the previous recorded price (monitoring only)
firstSeenAt	date	When this watchlist first saw this listing (monitoring only)
lastSeenAt	date	When this watchlist last saw this listing: this run for a live row, the last sighting for a gone row (monitoring only)
daysListed	number	Days from first to last sighting (monitoring only)
lastPrice	number	Gone rows only. The last price seen before the listing went
gonePresumedSold	boolean	Gone rows only. true when the listing was seen on 2+ consecutive runs and its last price was at or under this run's median
url	text (link)	Permanent listing link
scrapedAt	date	When this row was fetched

Deselect any field in the Input tab's column picker to drop it from every row — query, found, status, message, and scrapedAt always stay.

Pricing

• Listing returned: $2 per 1,000 listings
• Listing details fetched: $1 per 1,000 listings

Plus a $0.003 start fee per run. Each event above is billed independently, only when it actually returns data — misses (found:false) are never charged.

listing-details only fires when "Fetch extra details per listing" is on, and only for listings actually delivered that run — a listing dropped by monitoring never triggers a details fetch, so you never pay for a detail hop on a row you didn't get.

Gone listings ("Alert on gone listings") are ordinary listing rows: they count in listingCount and are billed at the listing rate above. There is no separate event, and a gone row never makes a request (no item page, no listing-details charge): it is rebuilt from what the watchlist saved the last time it saw the listing.

Monitoring / only new results

Turn on "Only return results that are new, or dropped in price" and a search line becomes a watchlist instead of a one-off dump:

• A listing counts as new the first time its Blocket listing ID is returned by this watchlist.
• A listing counts as a price drop when its price falls by at least "Minimum price drop" (5% by default) since it was last seen — measured against the most recently seen price, so a listing that drops twice is compared against its latest price each time, not its original one.
• Already-seen, unchanged listings are dropped before you're billed. A quiet run — nothing new, nothing cheaper — still finishes and returns one free row with monitorStatus: NO_NEW_ROWS, so a scheduled task shows it actually ran.
• The first run has nothing to compare against. By default it returns everything it finds as "new" (so you see your whole current search result once). Turn on "Seed silently" to instead have the first run bank everything quietly with zero rows and zero charge, and start alerting from the second run on — this is what stops a fresh watchlist from firing a hundred "new listing" messages into your Discord channel on day one.
• A listing counts as gone when the watchlist saw it before and this run's fetch should have shown it but didn't. Gone rows are returned only with "Alert on gone listings" on; they are counted for goneCount and sellThroughRate either way. See the next section.
• Sort is forced to Blocket's own newest-first order whenever monitoring is on, so two runs of the same watchlist are always comparing the same ordering.

Schedule recipe. Save this actor as an Apify Task with deltaMode: true and a deltaName you choose, add an hourly (or daily) Schedule, and point the task's webhook at Discord, Slack, Google Sheets, or an n8n/Make webhook URL to get pinged only when something actually changes.

Price-drop window limitation. A price drop is only ever seen while the listing is still inside what a run actually fetches — if a listing falls out of your maxListingsPerSearch window or your price filters between runs, this actor has no way to notice it dropped. Keep searches reasonably narrow (a specific model, a tight category) rather than one huge catch-all if price-drop coverage matters to you.

Sold signal and sell-through

Honesty note first: Blocket never confirms a sale. A gone row means the listing was delisted since this watchlist last saw it: most often sold, sometimes withdrawn, deleted by the seller, expired, or edited so it no longer matches your search words or price filters (Blocket filters on its side, so a listing re-priced out of your price band drops out of the results the same way). That is all gone claims.

Presumed sold. gonePresumedSold: true when the gone listing was seen on 2 or more consecutive runs and its last price was at or under this run's medianPrice. A listing priced at or below the going rate that stayed up and then vanished is the likeliest sale. Anything else is gone only.

How gone is detected. A run only reads the top of Blocket's newest-first feed, so a listing that slid below it is still for sale. The actor uses two checks:

1. Complete fetch. When the run fetched every listing Blocket counts for the search (its own "hittar du N annonser" number) with no failed page, any remembered listing missing from it is gone.
2. Feed position. Blocket's date order is by "published or renewed" date, newest first. Each run checks that order against the listing cards' own ages ("6 min", "2 tim") before it trusts it. The actor remembers each listing's position. A listing from the last run that is missing now is gone only if the listings that arrived above it (new ones, plus older ones a seller renewed back to the top) could not have pushed it out of what this run fetched, with a safety margin of 2 places or 5%. Listing ids are not used, because renewed old listings sit among new ones and an id cut-off would call still-listed ones sold.

"Betald placering" (paid placement) cards are never ranked, and a remembered listing that moved into one counts as still listed. A listing repeated across two result pages is returned once.

Limits. The signal favours precision over recall:

• A listing near the bottom of what a run fetches, or right at a 53-listing page boundary, is never called gone that run. For a busy search, set maxListingsPerSearch comfortably above the number of new listings between two runs, or narrow the search.
• There is no gone check on a first run, a run where a page was blocked or failed, an empty fetch, a run where the card ages could not confirm newest-first order (unless the fetch was complete), or one run after you change the filters of a named watchlist.
• A listing that comes back after being called gone (a seller relisting it, for example) is taken off the gone count and not alerted again.
• sellThroughRate is gone divided by tracked over the watchlist's lifetime, within its memory: listings unseen for 30 days are forgotten, and each watchlist remembers at most 5,000 listings.

Billing. Gone rows are ordinary listing rows, billed at the listing rate. There is no separate event and no extra request per gone row.

Example: track what sells, without new-listing alerts. Schedule this daily; sold signals start on run 2.

{
  "searches": ["iphone 15 pro"],
  "maxListingsPerSearch": 100,
  "deltaMode": true,
  "deltaName": "iphone15-sell-through",
  "alertOnNew": false,
  "alertOnPriceDrop": false,
  "alertOnGone": true
}

How to use

1. In the Apify Console. Open the actor page and click Start — the searches field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~blocket-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"searches":["iphone"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

4. Turn on "Only return results that are new, or dropped in price" under Monitoring once you want a watchlist instead of a one-off dump — see "Monitoring / only new results" above.

Input

{
  "searches": [
    "iphone"
  ]
}

One per line — plain keywords (e.g. "iphone", "soffa") or a full search-results URL copied from blocket.se, including any filters it already has. No login required. Accepted formats: iphone, soffa, https://www.blocket.se/recommerce/forsale/search?q=cykel&price_to=2000.

Sample output

query	found	status	searchQuery	listingCount	totalAvailable	truncated	newCount	priceDropCount	detailsCount	monitorStatus	goneCount	sellThroughRate	medianPrice	listings	listingId	title	price	currency	condition	conditionRaw	conditionBucket	listingStatus	brand	imageUrl	description	city	category	changeType	isNew	previousPrice	priceDropPct	firstSeenAt	lastSeenAt	daysListed	lastPrice	gonePresumedSold	url	scrapedAt
iphone	true	OK	iphone	100	4699	true	0	0	0					<all listings found (full list)>	27204266	Apple iPhone 18 Pro 1 TB svart	22500	SEK	Used	https://schema.org/UsedCondition	good	available	Apple	https://images.blocketcdn.se/dynamic/default/item/27204266/3402db2d-7ad1-4544-9bf8-52d10a185157	Apple iPhone 18 Pro 1 TB svart												https://www.blocket.se/recommerce/forsale/item/27204266	2026-10-07T06:20:14.790Z

A search that finds nothing comes back as a row with "found": false and is never charged. A quiet monitoring run comes back as a row with "found": true, "monitorStatus": "NO_NEW_ROWS" and is also never charged.

How to filter

Every filter below is optional and off by default — leave it out and you get exactly the same rows as before. minPrice/maxPrice/includeKeywords/excludeKeywords already existed (the latter two match anywhere in the row — title, description, brand, condition, etc. — not just the title). This section adds conditions, availability, cities and brands. A filtered-out listing is dropped before it's fetched further and before it's billed — you never pay for a row you didn't get.

1. Only sold-condition-equivalent ("Used") iPhones under 5,000 SEK, cheapest first:

{
  "searches": ["iphone"],
  "maxPrice": 5000,
  "conditions": ["good"],
  "sort": "relevance"
}

conditions matches Blocket's own itemCondition (New → new, Refurbished → like_new, Used → good, Damaged → fair; no grade at all → unknown) — never guessed from the title. Blocket has no "new with tags" concept, so new_with_tags never matches anything here.

2. A named brand only:

{
  "searches": ["hörlurar"],
  "brands": ["bose"]
}

brands is a case-insensitive "contains" match against the listing's own brand field — no extra request, and this actor keeps paging (up to its normal page budget) until it has enough matching rows, not just enough rows looked at.

3. Exclude a keyword, with per-listing city (needs details on):

{
  "searches": ["cykel"],
  "excludeKeywords": ["trasig", "reservdelar"],
  "cities": ["stockholm"],
  "includeDetails": true
}

cities matches the listing's city as a case-insensitive "contains" — but city is only known once includeDetails fetches the item page, so cities narrows nothing when that's off (documented in the input's own help text). availability exists too, but Blocket's search feed never shows a sold listing (a sold one is simply delisted — see "Sold signal" above), so it's a no-op kept only for input-shape consistency with the rest of the portfolio.

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~blocket-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"searches":["iphone"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~blocket-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"searches":["iphone"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~blocket-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"searches":["{{search}}"]}, mapping the row's search into the searches array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "Blocket Scraper | Apify" — the agent will find and run this actor.

For monitoring, point the Task's webhook (Console → your Task → Webhooks) at a Discord or Slack incoming-webhook URL, a Google Sheets automation (via Zapier/Make/n8n listening for the webhook), or an n8n/Make workflow's own webhook trigger, so new listings and price drops land wherever you actually work instead of a dataset you have to remember to check.

Tips

• Start monitoring with "Seed silently" on for any watchlist you're setting up on a schedule — it avoids a wall of "new" alerts for your entire current search result on day one.
• Keep a monitored search reasonably narrow (a model, a tight category, a price band) — see "Price- drop window limitation" above for why a huge catch-all search misses price drops on listings that fall outside what gets fetched.
• Turn on "Fetch extra details per listing" only when you actually need city or category — it adds one request (and one listing-details charge) per delivered listing.
• A BLOCKED status means Blocket returned a 403, 429, or 503 — lowering "Max concurrency" or trying again shortly usually clears it; this actor doesn't need a proxy by default.
• Paste your own already-filtered Blocket search URL instead of rebuilding filters in this actor's Input tab — anything the URL already filters on carries straight through.

vs. Blocket's own bevakning, and vs. logiover/blocket-scraper

Blocket's own "bevakning" (saved-search) feature lives inside a Blocket account, sends alerts by email or app notification only, and isn't callable from a script, a Sheet, or an automation platform. This actor gives you the same "only tell me what's new" behavior as a plain HTTP call or a scheduled Apify Task with a webhook into whatever tool you actually use.

The current Apify Store leader for Blocket, logiover/blocket-scraper, is a car-listing-skewed actor with 47 users and zero reviews — a one-off dump, no monitoring mode. This actor works across any Blocket category, adds new-listing and price-drop monitoring as a first-class mode, and bills only for listings actually delivered.

	What it costs	What you get	Trade-off
This actor	Pay per listing returned; nothing for a miss or a quiet monitoring run	Any Blocket category, monitoring mode (new + price drop + gone), sold signal with sell-through rate and median price, optional city/category details	Posted-time and seller identity aren't available (Blocket doesn't expose them statically); "gone" is delisted, not a confirmed sale
Blocket's own bevakning	Free, inside a Blocket account	Email/app alerts for a saved search	Not callable from a script or automation platform; no price-drop alerting; no sold signal
Doing it yourself	Your time to build and maintain a scraper, a seen-listing store, and a price-tracking layer	The same data	This actor's JSON-LD parsing, monitoring state, and redaction are the maintenance burden it absorbs

Data & privacy

This actor reads public search results that anyone can see without logging in. It doesn't log in, solve CAPTCHAs, or reveal hidden contact details. Seller identity is off by default: Blocket doesn't expose a seller id, name, or type anywhere in the pages this actor reads, so none is output. Contact-info-like strings (emails, phone numbers) inside a listing's description are redacted to [redacted]. Turning on seller info in a future version of this actor would make you responsible for having a lawful reason to process it. Not affiliated with Blocket / Schibsted.

Is this allowed? It collects the same public listing data your browser shows, for the searches you choose. It's built for monitoring a search, not for copying the marketplace. Check that your use fits Blocket's terms and your local law.

FAQ

Why is a row empty, or why does found say false? Either the input line was blank (status: BAD_FORMAT), Blocket returned a 403/429/503 (status: BLOCKED), or the search matched nothing on Blocket right now (status: NOT_FOUND). Check the message column for the specific reason. None of these are billed.

Am I charged for a quiet monitoring run? No. When monitoring finds nothing new and no price drops, you get one row with monitorStatus: NO_NEW_ROWS and listingCount: 0 — Actor.charge() only fires when listingCount is greater than zero.

Does it find sold listings? What is the sell-through rate? Blocket doesn't publish sales, so no tool can confirm one. With monitoring and "Alert on gone listings" on, this actor reports listings that disappeared since the last run (changeType: gone), flags the likeliest sales (gonePresumedSold), and gives the watchlist's lifetime sellThroughRate (gone divided by tracked, 0 to 1) and this run's medianPrice. See "Sold signal and sell-through" for how it decides and its limits.

Does this return posted-time or seller name? No. Blocket's search and item pages don't serve either statically (confirmed directly against the live site) — this actor doesn't fabricate them. You get listing details (title, price, condition, brand, image, description) plus, with "Fetch extra details per listing" on, city and full category path from the item page.

What does "Fetch extra details per listing" actually fetch? One extra request per delivered listing to that listing's own Blocket item page, for its city, full category path, and full (redacted) description. It's billed as a separate listing-details event and is automatically skipped, at no charge, whenever the proxy configuration is set to RESIDENTIAL.

Can I paste my own filtered Blocket search instead of using this actor's price filters? Yes. Paste the full search-results URL from your browser's address bar as a search line — any filters already in it (price range, category) carry through unchanged.

Do I need to configure proxies? No. This actor uses Apify's default proxy configuration (no proxy group) out of the box — Blocket doesn't block plain requests from Apify's datacenter IPs. RESIDENTIAL is available as a fallback if that ever changes.

Can an AI agent call this directly? Yes. It's registered on the Apify MCP server — an agent in Claude, Cursor, or another MCP client can find and run it by name ("Blocket Scraper | Apify"), or you can call the REST endpoint shown above from any script or workflow tool.

Related actors

• DBA Scraper — the same search and monitoring shape for DBA.dk, Denmark's largest classifieds marketplace (same Schibsted/Vend platform family).