Blocket Scraper: Sweden New Listing Alerts
Pricing
from $1.00 / 1,000 listing returneds
Blocket Scraper: Sweden New Listing Alerts
Blocket.se scraper by keyword: get one row per listing (title, price, condition, brand, link). Turn on monitoring for only new listings and price drops since your last run, replacing Blocket's own bevakning alerts. No login required; empty searches and quiet monitoring runs are free.
Pricing
from $1.00 / 1,000 listing returneds
Rating
0.0
(0)
Developer
Adrian Voss
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
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. 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.
- Reads Blocket's own structured listing data. Every base field comes from the
seoStructuredDataJSON-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 |
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, 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) |
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
Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed
per item only when data is actually found and returned — see
.actor/pay_per_event.json for exact prices. A miss is 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.
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.
- 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.
How to use
- In the Apify Console. Open the actor page and click Start — the
searchesfield is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found. - 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"]}'
- 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.
- 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 | listings | listingId | title | price | currency | condition | brand | imageUrl | description | city | category | changeType | isNew | previousPrice | priceDropPct | firstSeenAt | url | scrapedAt |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| iphone | true | OK | <monitoring status (quiet / seeded runs)> | <all listings found (full list)> | <price (sek)> | <city (details only)> | <category (details only)> | <new / price-drop / seen> | <is this listing new?> | <previous price (sek)> | <price drop %> | 1970-01-01T00:00:00.000Z |
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.
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-detailscharge) per delivered listing. - A
BLOCKEDstatus 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), optional city/category details | Posted-time and seller identity aren't available (Blocket doesn't expose them statically) |
| 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 |
| 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 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).