Bunjang Scraper: Korea New Listing & Price Alerts

Watch a search, get only what's new. This actor runs your search against Bunjang's own open search API (bunjang.co.kr) — one of Korea's two biggest second-hand marketplace apps — and returns one clean row per listing: title, price, condition, location, 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.

Who it's for

A reseller or arbitrage buyer watching one category (phones, sneakers, electronics) for underpriced or newly-posted listings wants a live feed of what's actually on Bunjang right now, without refreshing the search page by hand. A market-research team tracking asking prices, 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.

Use it alongside joonggonara-listing-lookup and daangn-listing-lookup — all three Korean second-hand marketplaces in this catalogue share the same column names (listingId, title, price, currency, listingStatus, postedAt, city, sellerType, sellerHash, imageUrl, url) so their rows merge cleanly into one feed.

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.
• No competing monitoring actor. The current Apify Store leader for Bunjang, piotrv1001's scraper, has 22 lifetime users and no monitoring mode. Korea's DIY alert-bot scene (GitHub bots posting new Bunjang listings to Discord/Telegram) is the strongest signal of unmet demand found anywhere in this catalogue's Asia research.
• Reads Bunjang's own open JSON API directly. No HTML scraping, no anti-bot workaround needed — api.bunjang.co.kr serves plain JSON with real pagination, confirmed live (two consecutive pages overlapped on only 1 of 100 listings).
• 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.
• Paste a keyword or your own saved search URL. Type plain keywords (including Korean, e.g. "나이키"), or paste a bunjang.co.kr search URL you've already run in your browser.

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 Bunjang returned a real search response 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 Bunjang 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)
listingId	text	Bunjang's own listing ID (pid)
title	text	Listing title
price	number	Price in KRW, converted from Bunjang's own string-typed field
currency	text	Always KRW
listingStatus	text	for_sale on every listing this actor has observed live; any other value is reported as status_<code> rather than guessed
conditionCode	number	Bunjang's own raw condition code (1 or 2 observed live) — passed through as-is, since neither code reliably means "new" vs "used" in the titles sampled
city	text	Seller's neighbourhood, when Bunjang's listing carries one
sellerType	text	business when Bunjang's own bizseller or proshop flag is set, otherwise private
favouriteCount	number	How many users have favourited the listing
freeShipping	boolean	Bunjang's own free-shipping flag
isPromoted	boolean	true for a paid/ad listing
category	text	Bunjang's own category ID
postedAt	date	Listing's last-updated time, converted from Bunjang's unix timestamp
imageUrl	text (link)	Listing thumbnail image
sellerHash	text	Anonymous, stable hash of the seller's user ID
sellerId	text	Only with "Include raw seller ID" on. Bunjang's raw user ID
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 (m.bunjang.co.kr/products/<id>)
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.

Monitoring / only new results

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

• A listing counts as new the first time its Bunjang listing ID (pid) is returned by this watchlist.
• A listing counts as a price drop when its price falls by at least "Minimum price drop to alert on" (5% by default) since it was last seen — measured against the most recently seen price. Bunjang has no bidding system, so every listing's price is a real, comparable fixed price.
• Already-seen, unchanged listings are dropped before you're billed. A quiet run — nothing new, nothing cheaper — still finishes and returns one free row.
• The first run has nothing to compare against. By default it returns everything it finds as "new". Turn on "Skip alerts on the first run" to instead have the first run bank everything quietly with zero rows and zero charge, and start alerting from the second run on — this stops a fresh watchlist from firing a wall of "new listing" messages on day one.

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.

Coverage limitation. This actor pages up to 1,000 listings per search (10 requests of 100), so a narrow or moderately popular keyword is fully covered every run; an extremely high-volume keyword can still exceed that in-between runs. Bunjang's own newest-first sort (order=date) means the freshest listings are always fetched first, so monitoring stays reliable even when truncated is 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~bunjang-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 since the last run" under Monitoring once you want a watchlist instead of a one-off dump — see "Monitoring / only new results" above.

Input

{
  "searches": [
    "iphone"
  ]
}

One search per line — keywords like "iphone" or "나이키", or paste a bunjang.co.kr search URL. Accepted formats: iphone, 나이키, https://api.bunjang.co.kr/api/1/find_v2.json?q=iphone.

Sample output

query	found	status	searchQuery	listingCount	totalAvailable	truncated	newCount	priceDropCount	listings	listingId	url	title	price	currency	listingStatus	conditionCode	city	sellerType	favouriteCount	freeShipping	isPromoted	category	postedAt	imageUrl	sellerHash	sellerId	isNew	changeType	previousPrice	priceDropPct	firstSeenAt	scrapedAt
iphone	true	OK							<all listings found (full list)>	<bunjang listing id (pid)>			<price (krw)>			<condition (raw bunjang code)>							<last updated (date)>		<seller (anonymous hash)>	<seller id (only with seller info on)>	<is this listing new?>		<previous price (krw)>	<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.

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~bunjang-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~bunjang-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~bunjang-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 "Bunjang Scraper | Apify" — the agent will find and run this actor.

Tips

• Start monitoring with "Skip alerts on the first run" 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.
• conditionCode is Bunjang's own raw code, not decoded into "new"/"used" — the titles under both observed codes mix genuinely new and ordinary used items, so this actor doesn't invent a label the data can't support. Filter on keywords in the title (e.g. "새상품", "미개봉") if you need that.
• A BLOCKED status means Bunjang 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.
• Use all three Korean marketplace actors together (this one, joonggonara-listing-lookup, daangn-listing-lookup) for one alert feed across Korea's whole DIY-alert-bot territory — their shared column names make merging the three outputs straightforward in Sheets or n8n.

vs. piotrv1001's scraper

The current Apify Store leader for Bunjang, piotrv1001's actor, has 22 lifetime users and no monitoring mode. This actor 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	$2 per 1,000 listings; nothing for a miss or a quiet monitoring run	Monitoring mode (new + price drop), anonymous seller hash, permanent listing link, up to 1,000 listings per search	Condition is a raw code, not a decoded "new"/"used" label
piotrv1001's scraper	Unknown / no monitoring	A one-off dump	No monitoring
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 pagination and monitoring state 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: you get a private/business flag (sellerType) and an anonymous seller hash so you can group listings by seller without names — Bunjang's own search results carry no seller display name to expose in the first place. Turning on "Include raw seller ID" makes you responsible for having a lawful reason to process that personal data. Not affiliated with Bunjang / 번개장터.

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. South Korea's Supreme Court held in 2022 (case 2021Do1533) that scraping publicly available web data did not breach copyright or information-protection law — favourable context, not a substitute for checking that your own use fits Bunjang'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), Bunjang returned a 403/429/503 (status: BLOCKED), or the search matched nothing 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 listingCount: 0 — Actor.charge() only fires when listingCount is greater than zero.

Why is price a number when Bunjang's own API returns it as text? Bunjang's search API sends price, the listing ID, and a couple of other fields as JSON strings (confirmed live), not numbers — this actor converts them so a downstream price filter or a Sheets formula gets a real number, not text that only looks like one.

What does listingStatus: for_sale mean, and are there other values? Every listing sampled live across three different searches came back on-sale — this actor doesn't know of a documented way to ask Bunjang's own search API for sold items too. If that ever changes you may see a status_<code> value this actor hasn't mapped a label for yet — it's passed through rather than hidden.

Do I need to configure proxies? No. This actor uses Apify's default proxy configuration (no proxy group) out of the box — Bunjang doesn't block plain requests from Apify's datacenter IPs.

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 ("Bunjang Scraper | Apify"), or you can call the REST endpoint shown above from any script or workflow tool.

Related actors

• Joonggonara Scraper — the same search and monitoring shape for Joonggonara, Korea's other major second-hand marketplace.
• Daangn Scraper — the same shape for Daangn (Karrot Market), Korea's neighbourhood-scoped classifieds app.