Luxury Sale Tracker: SSENSE Price Drop Alerts

Every designer product on SSENSE's sale, one row each: sale price, retail price, discount %, category and a link. Filter by designer, minimum discount or maximum price, and switch on monitoring to be told when a price drops, a product goes on sale, comes back in stock, or leaves the sale, in Slack, Discord or Telegram.

It reads SSENSE's public sale listing pages. No login, no cookies, no API key, no images.

Who uses this

• Resellers who buy designer menswear and womenswear on sale to sell on again (Grailed, Vinted, Vestiaire): filter to the brands you resell and a minimum discount, get an alert when the price falls.
• Deal newsletters and Discord / Telegram channels that post designer sales: one run a day, an alert only for what changed.
• Shoppers and stylists watching one designer: put the name in the list and get that designer's sale items, cheapest first in your own sheet.

Try it in 30 seconds

Press Start with the pre-filled input. It reads the first page of SSENSE's men's sale (120 products) and returns one row per product. One request.

Example: one designer, deep discounts, a Discord alert

{
  "designers": ["Rick Owens", "Acne Studios"],
  "gender": "men",
  "minDiscountPct": 40,
  "deltaMode": true,
  "deltaName": "my-resale-watchlist",
  "alertOnChangeOnly": true,
  "notifyUrl": "<your Discord webhook URL>"
}

Each designer is read from SSENSE's own page for that designer, so this is two requests, not a scan of the whole sale. Run it daily on a schedule: the first run is the baseline, and from the second run you only get (and only pay for) the products that are new on sale, dropped in price, came back, or left the sale.

How to use

1. In the Apify Console. Open the actor page and click Start — the designers 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~luxury-sale-price-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"designers":["<example>"]}'
   

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.

Input

{
  "designers": []
}

One designer per line, written as SSENSE spells it. Leave empty for the whole sale section. Each designer is read from SSENSE's own page for that designer (one search each, up to 20), and only that designer's products are kept. Accepted formats: Rick Owens, Acne Studios, Comme des Garçons Homme, A.P.C..

Everything else is optional: gender (men or women), locale (en-us for USD, en-gb for GBP), minDiscountPct, maxPricePerItem, maxItems, maxPages, and the monitoring and alert fields (deltaMode, deltaName, alertOn, minPriceDropPct, alertOnChangeOnly, skipFirstRun, notifyUrl, notifyFormat, maxNotificationsPerRun).

What you get

Field	Meaning
store, gender	ssense, and the sale section (men or women).
brand, name, url	The designer, the product name and its SSENSE page (a link only: the actor never opens a product page).
currency, price	The price now, in the currency of the site version you chose.
originalPrice, discountPct	The retail price before the sale and the discount against it.
category	SSENSE's category path, for example Clothing > Tops > T-Shirts.
inStock	true when SSENSE lists the product as available.
checkedAt	When the run looked.
changeType, previousPrice, changePct, lowestEverSeen, firstSeenAt	Monitoring only: new-on-sale, price-drop, price-rise, back-in-stock, gone or unchanged, the price last time, the change in percent, the lowest price this watchlist has seen and when it first saw the product. Empty when monitoring is off.

Example output

query	found	status	store	gender	brand	name	url	currency	price	originalPrice	discountPct	category	inStock	checkedAt	changeType	previousPrice	changePct	lowestEverSeen	firstSeenAt	scrapedAt
example	true	OK									<discount (%)>						<change (%)>			1970-01-01T00:00:00.000Z

Monitoring in three steps

1. Switch on Track prices across runs and give the watchlist a name.
2. Schedule the actor daily. The first run is the baseline (turn on Seed silently if you do not want it returned or billed).
3. Paste a Discord or Slack webhook (or a Telegram bot link) into Send alerts to. After each billed row an alert goes out with the product, the sale price, the retail price and the link. The first run of a watchlist sends nothing.

A product is reported gone only when the run read the whole list to its last page and a product it remembered from the earlier run of that same list was no longer there. A run cut short by maxItems, maxPages or the time limit never reports gone.

Limits, stated plainly

• SSENSE only. Farfetch is not part of this actor yet.
• Listing pages only. The actor reads the sale listing and designer sale pages and nothing else: no product pages, no sizes, no images, no descriptions, no account, bag or checkout.
• Sale sections only. Men's and women's sale; not new arrivals, not kids.
• Designers are matched by name (accents, case and punctuation ignored): "Rick Owens" does not also return "Rick Owens DRKSHDW", which SSENSE lists as its own designer. Write the name as SSENSE spells it; a designer SSENSE has no sale page for comes back as not found and is not charged.
• Pages are scanned in SSENSE's own order, up to maxPages. With narrow filters raise maxPages (up to 20 pages, 2,400 products); the men's sale is about 40 pages.
• Prices are the site version's currency (US dollars on en-us, British pounds on en-gb). Changing the site version starts a fresh baseline for the products it shows.
• One request at a time, about one per second at most.
• SSENSE's terms of service prohibit automated data collection. You are responsible for how you use the data.

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.

FAQ

Do I pay for products my filters remove? No. Only the rows you receive are billed. A run that returns nothing costs the start fee only, plus nothing per product.

Why does an unchanged product cost nothing in monitoring? With Only return products that changed on, a product that did not move writes no row and is not billed.

Can I run men's and women's together? Run the actor twice (two tasks), once per section, with the same watchlist name pattern.

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~luxury-sale-price-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"designers":["<example>"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~luxury-sale-price-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"designers":["<example>"]} (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~luxury-sale-price-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"designers":["{{sale product}}"]}, mapping the row's sale product into the designers array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "SSENSE Sale Scraper: Price Drops & Discount Alerts" — the agent will find and run this actor.