KREAM Scraper - Korea Sneaker Resale Price API avatar

KREAM Scraper - Korea Sneaker Resale Price API

Pricing

from $2.00 / 1,000 results

Go to Apify Store
KREAM Scraper - Korea Sneaker Resale Price API

KREAM Scraper - Korea Sneaker Resale Price API

Scrape KREAM lowest-ask, highest-bid, premium & price history for sneakers, streetwear & luxury as clean English JSON. Spot Korea-vs-StockX/GOAT arbitrage. Pay-per-result resale-price API for resellers & market-intel teams.

Pricing

from $2.00 / 1,000 results

Rating

0.0

(0)

Developer

Seok June Park

Seok June Park

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Share

KREAM Ranking Scraper β€” Korea Resale Best-Sellers πŸ‘Ÿ

Scrape live resale best-seller rankings from KREAM (크림) β€” Naver-owned, Korea's #1 resale marketplace for sneakers, streetwear, and collectibles β€” as clean, structured JSON. Get the top-selling products with their rank, name, brand, price (KRW), trading volume, and category in one run. Built to power a daily Korean shopping-trend dashboard.

⚠️ Read this first β€” bot wall. KREAM's data API sits behind Naver's nfront WAF. Every scripted HTTP client (curl, curl_cffi/chrome impersonation, plain Node) gets a 403. This actor drives a real browser to get through and reads KREAM's server-rendered ranking payload. From a datacenter or non-Korean IP the WAF blocks the request. To run this reliably on the Apify platform you almost certainly need a Korean residential proxy (Apify Proxy: RESIDENTIAL, country=KR). See Requirements & honesty note below.


What it does

This actor opens KREAM's public ranking board in a real Chromium browser and reads every product on the board in rank order (top of the board = rank 1). KREAM is a Nuxt (Vue) server-rendered app, so the same ranking data its API returns is embedded in the page β€” this actor captures that payload and pulls:

  • The resale ranking β€” rank position exactly as KREAM orders it.
  • Product & brand β€” full product name and brand.
  • Market signal β€” cumulative trading volume (e.g. 거래 12.4만) and current price (KRW).
  • Category, link & image β€” KREAM category path, product URL, and thumbnail.

You choose the board with the period input:

periodBoardURL scraped
realtime (default)Live top-50 right nowkream.co.kr/?tab=home_ranking_v2
weekly7-day best-sellers…&date_range_filter=weekly
monthly30-day best-sellers…&date_range_filter=monthly

KREAM's ranking board is a top-50 per period, so maxItems caps at 50.

Why KREAM? KREAM is the dominant resale platform in Korea and a leading signal of what's hot in sneakers, streetwear, and collectibles. Its ranking β€” ordered by real trading activity β€” is a sharp pulse on Korean youth consumer demand. A daily snapshot feeds trend dashboards, demand forecasting, and drop/hype tracking.


Input

FieldTypeDescription
periodstringrealtime (default), weekly, or monthly. Which ranking board to scrape.
maxItemsintegerMax products to collect, in rank order from the top. Default 50, max 50 (the board is a top-50).
proxyConfigurationobjectProxy settings. Use a Korean residential proxy to run on Apify (see below).

Input example

{
"period": "weekly",
"maxItems": 50,
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": ["RESIDENTIAL"],
"apifyProxyCountry": "KR"
}
}

Output

Each ranked product is one dataset record. price_krw is the plain Korean-won price. rank is the product's position on the board (1 = top). trading_volume is KREAM's cumulative trade-count label as shown on the card (Korean units, e.g. 거래 12.4만 β‰ˆ 124,000 trades). category is KREAM's category path.

{
"source": "kream",
"rank": 1,
"product_id": "748804",
"name": "Nike Mind 001 Black Chrome",
"brand": "Nike",
"price_krw": 189000,
"trading_volume": "거래 8,900",
"category": "μ‹ λ°œ > μŠ€λ‹ˆμ»€μ¦ˆ",
"url": "https://kream.co.kr/products/748804",
"image_url": "https://kream-phinf.pstatic.net/…/p_xxxxx.png",
"scraped_at": "2026-07-15T11:03:22+09:00"
}

A full sample from a real run is in samples/sample-output.json.

FieldMeaning
sourceAlways "kream".
rankPosition on the ranking board (1 = top), for the chosen period.
product_idKREAM product id (from the /products/{id} link).
nameProduct name.
brandBrand name (e.g. Nike, Apple, IAB Studio), or null.
price_krwCurrent price in KRW.
trading_volumeCumulative trade-count label as shown on the card (Korean units), or null.
categoryKREAM category path (Korean), or null.
urlProduct detail page URL.
image_urlThumbnail image URL.
scraped_atISO-8601 timestamp (KST, UTC+9).

In the live test, the critical fields β€” rank, name, brand β€” populated on 50/50 records, along with product_id, price_krw, trading_volume, category, url, and image_url.


Use cases

  • Daily shopping-trend dashboard β€” snapshot the realtime/weekly/monthly board every morning to see what Korea is trading, and how ranks and prices move.
  • Hype & demand intelligence β€” track rank, price_krw, and trading_volume over time to spot rising products and resale momentum.
  • Sneaker / streetwear / collectible research β€” find fast-moving products and their brand and price profile for sourcing or market entry.
  • AI agents & datasets β€” feed a structured, ranked resale feed into trend models, dashboards, or LLM agents.

⚠️ Requirements & honesty note

KREAM's data API sits behind Naver's nfront WAF. Here is exactly what does and doesn't work, verified from a Korean IP:

  • βœ… Real browser from a Korean IP β†’ passes. This actor launches Chromium and reads KREAM's server-rendered ranking payload straight out of the page. A headless browser is enough for KREAM (unlike some bot walls) β€” no virtual display needed.
  • ❌ Scripted HTTP clients β†’ 403. curl, curl_cffi/chrome impersonation, and Node's own request stack all get blocked by nfront on the API. That's why this actor uses a browser.
  • ❌ Datacenter / non-Korean IP β†’ blocked (WAF returns 500/403 with an empty body). Apify's free plan runs on US datacenter IPs, which nfront blocks. To run this on Apify you need a Korean residential proxy β€” configure Apify Proxy with groups=RESIDENTIAL and country=KR in proxyConfiguration.

Bottom line: locally, from a Korean consumer connection, this runs with no proxy. On Apify (US datacenter), budget for a Korean residential proxy β€” without one, expect nfront blocks. likely_works_on_apify_us_datacenter = false without a KR proxy; this is by design of KREAM's protection, not a bug in the actor. The actor retries transient WAF 500s with backoff before giving up.

Advanced knobs (env vars, for local experimentation):

Env varEffect
KREAM_RANKING_SCRAPER_LITE_TEST=1Cap to ~8 items for a quick smoke test.
KREAM_RANKING_SCRAPER_HEADLESS=0Launch the browser headed (default is headless, which passes KREAM).

❓ FAQ

Is it legal to scrape this data? This actor collects only public, non-personal ranking data β€” the same board any visitor sees on kream.co.kr without logging in. No personal data is collected. You are responsible for how you use the data; see the legality note below.

Why does it need a Korean residential proxy on Apify? KREAM's nfront WAF blocks datacenter and non-Korean IPs. Apify's default/free datacenter IPs (US) get denied. A Korean residential proxy makes the request look like an ordinary Korean visitor. See Requirements.

How fresh is the data? Every run scrapes the live board at run time. The realtime board changes continuously; schedule the actor (e.g. daily) for a rolling resale-trend history.

What is NOT included? No seller/buyer PII, no bid/ask order book, no per-product deep detail β€” only what's on the public ranking board. brand, trading_volume, or category can be null for the occasional item that doesn't expose them.


πŸ€– Use with AI agents (MCP)

Call this Actor as a tool from Claude or any MCP-compatible AI agent β€” no glue code. Point your MCP client at Apify's server, scoped to this Actor:

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com?tools=kdatafactory/kream-ranking-scraper",
"headers": { "Authorization": "Bearer <YOUR_APIFY_TOKEN>" }
}
}
}

Your agent can then pull KREAM resale rankings and Korean shopping-trend data on demand β€” no scraping code in your app. Grab a free token from Apify β†’ Integrations.

πŸ‡°πŸ‡· More Korean data actors

This actor is part of a suite of Korean-platform scrapers by the same maintainer:

Browse all: apify.com/kdatafactory


Rate limiting & legality

  • The actor collects only public, non-authenticated data. It never logs in and never touches private or account endpoints.
  • No personal data is collected β€” only public ranking product attributes.
  • Requests are paced: one board load at a time, with backoff retries between attempts, to stay gentle on KREAM's servers.
  • You are responsible for using the data in line with KREAM's terms of service and applicable law.

Known limitations (honesty note)

  • Bot wall. KREAM is behind Naver's nfront WAF. This actor needs a real browser and, on Apify, a Korean residential proxy. Without those, runs will be blocked. likely_works_on_apify_us_datacenter = false without a KR proxy β€” this is by design of KREAM's protection, not a bug in the actor.
  • Board size. The ranking board is a top-50 per period; maxItems above 50 simply returns the 50 available.
  • Fallback path. If KREAM changes its page and the ranking payload can't be parsed, the actor falls back to reading the rendered ranking cards β€” on that path brand and category come back null (they aren't exposed in the rendered card), while rank, name, price_krw, trading_volume, and image_url are still returned.
  • Korean strings. category and trading_volume are Korean-language labels as KREAM shows them.

If this actor saves you time, a rating on the Store page helps a solo maintainer a lot. Found an issue? Open it in the Issues tab β€” I respond fast.