Rebag Luxury Resale Scraper

---

🎯 What this scrapes

Rebag is a well-known name in luxury handbag resale, and its Apify Store coverage is thin: jungle_synthesizer/rebag-luxury-resale-listings-scraper runs with just 4 users, and only 3 rivals name-match the target at all. This Actor talks to Rebag's public Shopify storefront JSON feed on shop.rebag.com — never the client-rendered, robots.txt-disallowed www.rebag.com/shop page — for normalized designer, condition, price, SKU/item-number, image, and spec data per variant (not per product, since price and availability live at the variant level), backed by a three-tier fallback (collection guess, free-text suggest, full-catalog browse) and per-product/variant fault isolation.

🔥 What we handle for you

• 🌐 Proxy session rotation via Apify Proxy — fresh session and exit IP on every block.
• 🔁 Retries with exponential backoff on 408 / 429 / 5xx — up to 5 attempts per page, Retry-After honoured.
• 🧱 Product- and variant-level fault isolation — one malformed product or variant is skipped and logged, never crashes the run.
• 🧊 Clean, typed dataset rows — validated fields, ISO-8601 timestamps, one row per variant so price and availability never get flattened away.
• 💰 Pay per output — no Actor start fee. You pay for the output events listed in Pricing.

💡 Use cases

• Price-comps and arbitrage bots — pull normalized per-variant pricing and condition to feed a resale price model.
• Authenticators and appraisers — cross-reference SKU/item-number, brand code, and spec fields against a catalog of known listings.
• Resellers sourcing inventory — filter by designer and condition to shortlist candidates worth reselling elsewhere.
• Market researchers — track designer mix, condition distribution, and pricing trends across Rebag's resale catalog.

⚙️ How to use it

1. Click Try for free at the top of the page.
2. Fill in the input form — most fields have sensible defaults.
3. Click Start. Output streams into the run's dataset.
4. Export from Storage → Dataset as JSON, CSV, or Excel — or fetch via the API.

📥 Input

Field	Type	Required	Default	Notes
query	string	no	'chanel'	Free-text designer/item query (e.g. 'chanel', 'chanel classic flap'). Slugified into a candidate collection handle…
collectionHandle	string	no	None	Advanced override — exact Shopify collection handle (lowercase letters, digits, hyphens only), bypasses slugification…
maxItems	integer	no	200	Cap on rows this run, across all pages/fallback.
designerFilter	string	no	None	Case-insensitive substring match against the designer/vendor, applied post-fetch.
conditionFilter	string	no	None	Case-insensitive substring match against the parsed condition (e.g. 'Very Good'), applied post-fetch.
proxyConfiguration	object	no	{'useApifyProxy': True}	Apify Proxy is enabled by default; your selected proxy settings are used as configured.

Example input

{
  "query": "chanel",
  "maxItems": 5,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

📤 Output

Every row is one dataset item.

Field	Type	Notes
listing_id	string	variant.id — unique key, not the product id.
product_id	string	Product id.
sku	['string', 'null']	variant.sku (Rebag's item number).
title	string	Product title.
designer	string	vendor (designer/brand).
category	['string', 'null']	product_type.
condition	['string', 'null']	Parsed from variant.option1/title, falling back to the bc-filter-
color	['string', 'null']	variant.option2.
price	['number', 'null']	variant.price, decimal string parsed to float.
compare_at_price	['number', 'null']	variant.compare_at_price; null when not discounted.
available	boolean	variant.available.
primary_image_url	['string', 'null']	images[0].src.
image_urls	array	All images[].src (empty OK).
specs	object	Best-effort Label: value pairs parsed from body_html (empty OK).
description_html	['string', 'null']	Raw body_html.
tags	array	Product tags (empty OK).
product_url	string	https://shop.rebag.com/products/{handle}
published_at	['string', 'null']	Product published_at, ISO 8601 as returned.
scraped_at	string	ISO 8601 UTC row-creation timestamp.

Example output

{
  "listing_id": "45063759954097",
  "product_id": "8212143341745",
  "sku": "319168/1",
  "title": "Women's Pointed Toe Pumps Satin and Lucite",
  "designer": "Chanel",
  "category": "Shoes",
  "condition": "Very Good",
  "color": "blue",
  "price": 270.0,
  "compare_at_price": null,
  "available": true,
  "primary_image_url": "https://cdn.shopify.com/...",
  "image_urls": [
    "https://cdn.shopify.com/..."
  ],
  "specs": {
    "Model": "...",
    "Exterior Material": "Satin",
    "Exterior Color": "Blue",
    "Interior Material": "Leather",
    "Interior Color": "Blue",
    "Brand Code": "G26724",
    "Item Number": "319168/1"
  },
  "description_html": "<p>...<b>Condition:</b> Very good. ...</p>",
  "tags": [
    "100-to-500",
    "bc-filter-Great",
    "bc-filter-Excellent",
    "chanel",
    "in-stock"
  ],
  "product_url": "https://shop.rebag.com/products/shoes-chanel-womens-pointed-toe-pumps-satin-and-lucite-3191681",
  "published_at": "2025-01-14T00:42:08-05:00",
  "scraped_at": "2026-08-24T12:00:00+00:00"
}

💰 Pricing

No Actor start fee. You pay for the output events below.

Event	USD per event	Billing unit
result-row	$0.0012	Charged for each listing row (one Rebag variant) written to the dataset, deduped by listing_id.

1,000 output events cost $1.20 at the standard rate, with no start charge.

Existing subscriber discounts remain available in the Apify Pricing tab.

🚧 Limitations

v1 covers shop.rebag.com's public storefront JSON feed only — no authenticated/account-only data (order history, saved items), no historical price tracking, and no canonical closed list of condition values (Condition ships as free text since the platform's full vocabulary wasn't exhaustively confirmed). The specs field is a best-effort regex extraction from each product's description HTML — description_html always ships alongside it as the raw fallback.

❓ FAQ

Do I need a Rebag account or API key?

No. This Actor scrapes Rebag's own public Shopify storefront JSON feed — no login, no API key.

What happens if my query doesn't match a real collection?

We fall back to Rebag's free-text search endpoint (capped at 10 results by the platform itself) so you still get something instead of a guaranteed-empty run.

Why is one product several rows in my dataset?

Price, SKU, and availability live at the variant level (color, sometimes size), so we emit one row per variant, not one per product page.

Can I browse the whole catalog without a query?

Yes — leave Query and Collection handle both empty and we page through the full public catalog up to Max items.

💬 Your feedback

Spotted a bug, hit a weird edge case, or need a new field? Open an issue on the Actor's Issues tab on Apify Console — we ship fixes weekly and we read every report.

---