# KREAM Korea Scraper | Sneakers, Fashion & Price History (`abotapi/kream-scraper`) Actor

Scrape KREAM (kream.co.kr) sneaker and fashion resale data by keyword search, filters, sorts, or product URLs. Extract 34+ fields, including lowest ask, highest bid, market price, premium, retail price, style code, sizes, and optional price history.

- **URL**: https://apify.com/abotapi/kream-scraper.md
- **Developed by:** [Abot API](https://apify.com/abotapi) (community)
- **Categories:** E-commerce, Automation, Developer tools
- **Stats:** 16 total users, 3 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 product results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## KREAM Scraper — Sneaker & Fashion Resale Prices

Scrape **KREAM (kream.co.kr)**, Korea's #1 sneaker and fashion resale marketplace, for live resale prices and product data. Search by keyword with full sorts and filters, or paste product URLs. Returns **45+ fields per product** — lowest ask, highest bid, market price, last sale, premium, sales count, retail price, style code, release date, colorway, every size, wish/review counts and the full image set — **without** needing a separate detail fetch.

### Why this scraper

| | This actor | Typical KREAM scrapers |
|---|---|---|
| Fields per product | **45+** | ~8 (listing) / ~14 with detail |
| Market data (ask/bid/premium/sales) | ✅ on every item | ❌ |
| Style code, release date, retail, sizes | ✅ in base listing | detail-only (extra charge) |
| Sort options | **11** | up to 9 |
| Filters | quick delivery, below retail, sold-out, category, gender | up to 3 |
| Modes | keyword search + product URLs | search only |
| Speed & memory | Fast, low memory | Slower, memory-heavy |
| Detail enrichment | $0.0008/item | up to $0.005/item |

The base listing already includes the data most scrapers charge a detail fetch for, so you get more for the per-result price.

### Input

| Field | Description |
|---|---|
| `mode` | `search` (keyword) or `url` (paste KREAM URLs). Only the keyword source differs: the sort and filter fields below apply in **both** modes. |
| `keywords` | Search terms, e.g. `["nike dunk", "jordan 1"]`. Search mode only; in URL mode the keyword is read out of each pasted search URL instead. |
| `sort` (both modes) | `popularity`, `lowest_ask`, `highest_bid`, `wish`, `style_tags` (most reviewed), `date_released`, `discount_rate`, `premium_high`, `premium_low`, `male_popularity`, `female_popularity`. |
| `quickDelivery` (both modes) | Only products with KREAM Quick Delivery (express) stock. |
| `belowRetail` (both modes) | Only products whose lowest ask is below brand retail. |
| `excludeSoldOut` (both modes) | Drop products with no live ask. |
| `category` (both modes) | Optional KREAM category slug (e.g. `sneakers`). |
| `gender` (both modes) | `men`, `women`, `kids` or any. |
| `urls` | KREAM product URLs (`/products/<id>`) or search URLs (URL mode). The sort and filter fields marked *(both modes)* are **not** ignored here: each pasted search URL is re-run through KREAM's search with them applied. A pasted product URL is the one exception, returning that single product in full. |
| `fetchDetails` | Add price history (5 spans), per-size ask/bid, and recent sales/asks/bids. |
| `maxItems` | **The cap.** Stop after this many products (default 20; 0 = unlimited). |
| `maxPages` | Page-walk safety bound. Leave empty (0) for no page limit — the run stops at **Max items**, not here. |
| `resumeFromRunId` | Paste a previous run ID or dataset ID to continue a large crawl without returning/charging for products already collected there. Continues ONE specific interrupted run. |
| `incrementalMode` | Turn on for daily/weekly recurring monitoring of the same search. First run: everything is `NEW`. Later runs: only `NEW`/`UPDATED`/`REAPPEARED` products by default. State is kept per search/URL/sort/filter setup (see below). |
| `stateKey` | Optional. Name an incremental-mode monitoring campaign, or share state deliberately across differently-configured runs. Leave empty to derive a key automatically from the search scope. |
| `emitUnchanged` | Incremental mode only. Off by default — also return (and bill) products marked `UNCHANGED`. |
| `emitExpired` | Incremental mode only. Off by default — also return (and bill) products marked `EXPIRED` (present before, not found this run). Only produced after a run that fully scanned the tracked search (not capped, not blocked, not a Resume). |
| `proxy` | Apify Residential recommended. |
| `mcpConnectors` | Optionally pipe results into Notion / Linear / Airtable / Apify via MCP. Never changes the dataset. |

### Output (per product)

`productId`, `url`, `productName`, `productNameKo`, `brand`, `brandId`, `category`, `categoryName`, `styleCode`, `colorway`, `gender`, `releaseDate`, `retailPrice`, `retailPriceFormatted`, `currency`, `imageUrl`, `imageUrls`, `lowestAsk`, `highestBid`, `marketPrice`, `lastSalePrice`, `totalSales`, `changeValue`, `changePercentage`, `premium`, `premiumPercentage`, `hasImmediateDelivery`, `wishCount`, `reviewCount`, `haveCount`, `isActive`, `isTradable`, `sizes`, `sizeOptions`.

With `fetchDetails`: `priceHistory` (1m/3m/6m/1y/all series), `inventoryBySize` (per-size lowest ask / highest bid), `recentSales`, `recentAsks`, `recentBids`.

With `incrementalMode`: `changeType` (`NEW`/`UPDATED`/`UNCHANGED`/`REAPPEARED`/`EXPIRED`), `changedFields` (which fields moved since last run), `firstSeenAt`, `lastSeenAt`.

Prices are in **KRW**.

### Resume & recurring updates

Two different tools for two different jobs:

- **Resume** (`resumeFromRunId`) continues ONE specific interrupted or capped run — paste a run ID or
  dataset ID and this run skips every `productId` already collected there.
- **Incremental mode** (`incrementalMode`) is for scheduling this same search again and again (e.g. daily) and
  getting only what changed. The actor keeps its own baseline in a key-value store, keyed on a hash of the
  search/URL scope, sort, filters and `fetchDetails` (`maxItems`/`maxPages` are output caps, not scope, and are
  excluded — a 5-item run and a 50-item run of the same search share one baseline). Set `stateKey` to name or
  share a campaign explicitly.
- **Identity key:** `productId` (the same field already used for in-run dedup).
- A field only counts as changed when both old and new values are present and differ (`changed(a,b) := a != b
  and a is not None and b is not None`) — a value that goes missing then comes back is not itself a "change".
- **Prices and `wishCount` are real signal on a resale marketplace, not noise** — an ask/bid/wish move IS
  reported as `UPDATED`, never normalized away.
- `EXPIRED` is only ever emitted after a run that reached the natural end of every tracked keyword/URL (not
  capped by Max items, not a Resume, not blocked) — a partial scan can't tell "gone" from "not reached yet".

### Connection & reliability

KREAM gates its API by request headers, not by IP geography — so **any residential country works** (no Korea pin needed). Use **Apify Residential** for the best success rate.

> ⚠️ **Datacenter / free-tier:** these connections are more likely to be refused, lowering the success rate and possibly returning zero items. Switch the Proxy setting to Apify Residential if you see repeated refusals.

### Pricing (pay-per-event)

| Event | Price |
|---|---|
| Actor start | $0.08 |
| Product result | $0.003 |
| Detail enrichment (only when `fetchDetails` is on) | $0.0008 |

### Notes

- Korean product names are kept in `productNameKo`; the romanised/English name is `productName`.
- This is an unofficial scraper; respect KREAM's terms and applicable law.

# Actor input Schema

## `mode` (type: `string`):

How to start the scrape. 'search' runs KREAM keyword searches. 'url' processes the KREAM URLs you paste (product URLs are fetched as full detail; search URLs are paged). Only where the keyword comes from differs: the sort and filter fields apply in BOTH search mode and URL mode, to every pasted KREAM search URL as well.

## `keywords` (type: `array`):

One or more keywords to search KREAM for (e.g. 'nike dunk', 'jordan 1', 'stussy'). Each keyword is scraped independently. Search mode only: in URL mode the keyword is read out of each pasted KREAM search URL instead, and this field is not used.

## `urls` (type: `array`):

Paste KREAM product URLs (https://kream.co.kr/products/<id>) or search URLs (https://kream.co.kr/search?keyword=...). Product URLs return full detail; search URLs page forward automatically. The sort and filter fields below are NOT ignored here: every pasted search URL is re-run through KREAM's search API with them applied. A pasted product URL is the one exception, since it returns that single product in full.

## `sort` (type: `string`):

Order KREAM returns results in. Applies in BOTH search mode and URL mode: the search request is rebuilt for a pasted KREAM search URL, so this sort is sent with it. A pasted product URL returns that single product, so ordering does not apply to it.

## `quickDelivery` (type: `boolean`):

Only return products with KREAM Quick Delivery (express) inventory available. Applies in BOTH search mode and URL mode: it is sent as a server-side parameter on the search request built for a pasted KREAM search URL too. A pasted product URL always returns that one product unfiltered.

## `belowRetail` (type: `boolean`):

Only return products whose lowest ask is below the brand's retail (original) price. Applies in BOTH search mode and URL mode: products found through a pasted KREAM search URL are filtered by it as well. A pasted product URL always returns that one product unfiltered.

## `excludeSoldOut` (type: `boolean`):

Drop products with no live lowest ask (nothing currently buyable). Applies in BOTH search mode and URL mode: products found through a pasted KREAM search URL are filtered by it as well. A pasted product URL always returns that one product unfiltered.

## `category` (type: `string`):

Optional KREAM category slug to narrow results (e.g. 'sneakers'). Leave empty for all categories. Applies in BOTH search mode and URL mode: it is sent as a server-side parameter on the search request built for a pasted KREAM search URL too. A pasted product URL always returns that one product unfiltered.

## `gender` (type: `string`):

Optional gender filter. Applies in BOTH search mode and URL mode: it is sent as a server-side parameter on the search request built for a pasted KREAM search URL too. A pasted product URL always returns that one product unfiltered.

## `fetchDetails` (type: `boolean`):

Visit each product's detail endpoint to add price history and per-size ask/bid inventory. Slower and adds a small per-item charge. Most fields (style code, release date, retail, sizes, market prices) are already included without this.

## `maxItems` (type: `integer`):

The single cap on this run: stop after collecting this many products (across all keywords/URLs). Set 0 for unlimited.

## `maxPages` (type: `integer`):

Safety bound on how many result pages to walk per keyword. Leave empty (0) for no page limit — the run stops at Max items, not here. Does not impose a separate cap below Max items.

## `resumeFromRunId` (type: `string`):

Paste a previous run ID or dataset ID to continue a large crawl of products without returning or charging for products already collected there. Use this after an interrupted or capped run. For recurring monitoring of the same search, use Incremental mode below instead.

## `incrementalMode` (type: `boolean`):

Turn this on for daily/weekly recurring monitoring of the same search. The first run returns all matching products as NEW. Later runs normally return only NEW, UPDATED, and REAPPEARED products (price/ask/bid/wish changes ARE reported — they are the real signal on a resale marketplace). Turn on "Emit unchanged" or "Emit expired" only when you also want those products returned (and billed). State is kept separately per search/URL/sort/filter setup; use State key to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from a previous run above.

## `stateKey` (type: `string`):

Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently-configured runs. Leave empty to let the actor derive a key automatically from the keyword/URL, sort and filter settings — different searches then never mix state with each other.

## `emitUnchanged` (type: `boolean`):

Off by default. Turn on to also return products that have not changed since the last run, marked UNCHANGED. This returns — and bills — extra rows you already have, so leave it off unless you specifically want the full snapshot every run.

## `emitExpired` (type: `boolean`):

Off by default. Turn on to also return products that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked search — not when Max items capped it, Resume was used, or the run was blocked. This returns — and bills — extra synthetic rows, so leave it off unless you need expiry tracking.

## `proxy` (type: `object`):

Use Apify Residential proxy for reliable results. A country pin is optional.

## `mcpConnectors` (type: `array`):

Optionally send results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize one under Apify → Settings → API & Integrations, then select it here. Notion gets a rich page-per-item export; other connectors get a best-effort write/digest. Leave empty to skip; never changes the dataset output. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).

## `notionParentPageUrl` (type: `string`):

URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.

## `maxNotifyListings` (type: `integer`):

Cap on items written to each connector per run. Does not affect the dataset.

## Actor input object example

```json
{
  "mode": "search",
  "keywords": [
    "nike"
  ],
  "urls": [
    "https://kream.co.kr/products/23879"
  ],
  "sort": "popularity",
  "quickDelivery": false,
  "belowRetail": false,
  "excludeSoldOut": false,
  "gender": "",
  "fetchDetails": false,
  "maxItems": 20,
  "maxPages": 0,
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "maxNotifyListings": 50
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "mode": "search",
    "keywords": [
        "nike"
    ],
    "urls": [
        "https://kream.co.kr/products/23879"
    ],
    "maxItems": 20,
    "incrementalMode": false,
    "emitUnchanged": false,
    "emitExpired": false,
    "proxy": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("abotapi/kream-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "mode": "search",
    "keywords": ["nike"],
    "urls": ["https://kream.co.kr/products/23879"],
    "maxItems": 20,
    "incrementalMode": False,
    "emitUnchanged": False,
    "emitExpired": False,
    "proxy": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("abotapi/kream-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "mode": "search",
  "keywords": [
    "nike"
  ],
  "urls": [
    "https://kream.co.kr/products/23879"
  ],
  "maxItems": 20,
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call abotapi/kream-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,abotapi/kream-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/xb9yaUWSxK993aaa6/builds/VAPdsP2DzfkXtqgGv/openapi.json