Zigzag Scraper — Korean Women's Fashion Search & Prices avatar

Zigzag Scraper — Korean Women's Fashion Search & Prices

Pricing

from $4.00 / 1,000 results

Go to Apify Store
Zigzag Scraper — Korean Women's Fashion Search & Prices

Zigzag Scraper — Korean Women's Fashion Search & Prices

Scrape Zigzag (지그재그), Korea's largest women's fashion marketplace with 8,000+ shops. Keyword search or ranked feeds via Zigzag's own GraphQL API: product name, shop, KRW price, discount rate, review score and count, image and URL as clean JSON. For K-fashion research and price monitoring.

Pricing

from $4.00 / 1,000 results

Rating

0.0

(0)

Developer

Seok June Park

Seok June Park

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

2

Monthly active users

14 days ago

Last modified

Share

Zigzag Product Scraper 👗

Scrape searched and ranked women's-fashion products from Zigzag (지그재그) — Korea's largest women's-fashion marketplace, aggregating 8,000+ shops — as clean, structured JSON. Get product names, shop names, KRW prices, discount rates, review scores, review counts, and images in one call.

Built for K-fashion trend research, dropshipping product sourcing, and price monitoring.

Try it free. Apify's free plan includes $5 of monthly platform credit — roughly 1,250 results from this actor, no credit card required. Set your input, click Start, and export JSON/CSV/Excel.


What it does

This actor pulls product data directly from Zigzag's public GraphQL API — the same GetSearchResult operation that powers the zigzag.kr web app — so results are fast and complete, with clean cursor pagination. Two modes:

  • Search — every product matching a keyword (e.g. 원피스 dress, 니트 knit, nike, 가디건 cardigan).
  • Ranking — the same keyword feed, but each product is assigned a rank from its position in Zigzag's default recommendation order (Zigzag ranks its feed by a popularity/relevance blend).

Input

FieldTypeDescription
modestring"search" or "ranking".
querystringThe search keyword. Required. e.g. 원피스, 니트, nike.
maxItemsintegerMax products to collect. Default 100.
proxyConfigurationobjectApify Proxy settings. Optional — runs direct if omitted.

Input example

{
"mode": "ranking",
"query": "원피스",
"maxItems": 100
}
{
"mode": "search",
"query": "니트",
"maxItems": 200
}

Output

Each product is one dataset record. Prices are in KRW (Korean won). rating is Zigzag's review score (0–5). rank is populated in ranking mode only.

Prices are reconstructed from Zigzag's final_price (what the customer pays) and discount_rate: when a product is discounted, price_krw is the original list price and sale_price_krw is the discounted price; when not discounted, price_krw holds the price and sale_price_krw is null.

{
"source": "zigzag",
"product_id": "169746777",
"name": "[🤍여름/MADE]라미 쉬폰 미니 원피스(+NEW컬러)(미니원피스 하객룩 여름원피스)",
"brand": "메이빈스",
"price_krw": 69895,
"sale_price_krw": 39840,
"discount_rate": 43,
"rating": 4.8,
"review_count": 111,
"category": null,
"rank": 1,
"url": "https://store.zigzag.kr/app/catalog/products/169746777",
"image_url": "https://cf.image-farm.s.zigzag.kr/original/ad/2026/6/12/202606121459580334_46155.png?width=720&height=720&quality=80&format=jpeg",
"scraped_at": "2026-07-09T10:00:46+09:00"
}

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

FieldMeaning
sourceAlways "zigzag".
product_idZigzag catalog product id.
nameProduct name.
brandShop / brand storefront name on Zigzag.
price_krwOriginal list price (KRW).
sale_price_krwDiscounted price if on sale, else null.
discount_ratePercent off (integer), or null when not discounted.
ratingZigzag review score, 0–5 (null if none).
review_countNumber of reviews (null if none).
categoryAlways null — the search feed carries no per-item category label.
rankPopularity/relevance rank (ranking mode only).
urlProduct page URL.
image_urlThumbnail image URL.
scraped_atISO-8601 timestamp (KST, UTC+9).

A note on what this actor does not return

To keep the data honest and privacy-safe, the actor deliberately does not sell fields that don't reliably populate or that identify people:

  • category is always null on the search feed — it is kept in the schema for contract compatibility but is not a sold field.
  • Seller/reviewer identity (nicknames, ids, profiles) is never collected — only shop storefront names and item/price data.

Use cases

  • K-fashion trend research — track which shops, styles, and price points dominate Zigzag's women's-fashion feed for a given keyword.
  • Dropshipping / product sourcing — build a catalog of trending Korean women's-fashion products with images, shops, and prices to source or resell.
  • Price & discount monitoring — watch price_krw vs sale_price_krw and discount_rate over time to catch drops and benchmark competitor pricing.
  • AI agents & datasets — feed structured fashion data into recommendation models, market dashboards, or LLM agents.

❓ FAQ

Is it legal to scrape this data? This actor collects only public, non-personal catalog data — the same product listings any Zigzag visitor sees without logging in. No personal data is collected. You are responsible for how you use the data; see the legality note below.

What does it cost in practice? $4.00 per 1,000 results + a few cents of platform usage. Example: a 500-result daily pull costs about $2.00/day. Apify's free $5 monthly credit covers ~1,250 results.

Do I need to configure proxies? No — the default settings work out of the box. A proxy only helps against genuine HTTP 403/429 rate limiting on heavy pulls (high maxItems); it cannot fix other failure modes. See the proxy note below for which is which.

How fresh is the data? Every run scrapes the live site at run time. Schedule the actor for recurring snapshots.

What is NOT included? category is always null — Zigzag's search feed carries no per-item category label, so it is kept only for schema compatibility. Seller/reviewer identity (nicknames, ids, profiles) is never collected — only shop storefront names and item/price data.


🤖 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/zigzag-scraper",
"headers": { "Authorization": "Bearer <YOUR_APIFY_TOKEN>" }
}
}
}

Your agent can then pull Zigzag women's-fashion search results 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 endpoints.
  • No personal data is collected — no seller or reviewer names, profiles, or IDs. Only shop storefront names and item/price data.
  • Requests are rate-limited: one page at a time with a ≥ 500 ms delay between requests, to stay gentle on Zigzag's servers.
  • You are responsible for using the data in line with Zigzag's terms of service and applicable law.

⚠️ Proxy recommendation

A proxy is optional, and only helps against one specific failure. The actor uses the proxy configuration you provide (via proxyConfiguration in input) and falls back to a direct connection when none is set or the tunnel is down.

When a residential proxy helps: repeated GraphQL HTTP 403 or HTTP 429 in the log. That is genuine rate limiting or an IP block, and switching on Apify Proxy with the RESIDENTIAL group — and/or lowering maxItems — is the right response.

When it does not help: an error reporting an empty body on an HTTP 200 (x-cache: Error from cloudfront), or a GraphQL contract mismatch. Those are request-shape rejections at Zigzag's CDN edge and they reproduce identically on residential, datacenter and direct connections — buying residential traffic cannot fix them. The actor's error message now says which case it observed, so please just report the run instead of paying for proxy traffic that will not change the outcome.


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.