Veepee Scraper - Flash Sales, Prices, Discounts & Sizes avatar

Veepee Scraper - Flash Sales, Prices, Discounts & Sizes

Pricing

from $1.20 / 1,000 result rows

Go to Apify Store
Veepee Scraper - Flash Sales, Prices, Discounts & Sizes

Veepee Scraper - Flash Sales, Prices, Discounts & Sizes

Scrape Veepee flash sales: live campaigns with brands, dates and discounts plus per-sale items with price, was-price, discount %, sizes and availability across FR, IT, ES, BE and NL markets. Campaign discovery is anonymous; sale item detail uses a member session lane.

Pricing

from $1.20 / 1,000 result rows

Rating

0.0

(0)

Developer

Abot API

Abot API

Maintained by Community

Actor stats

1

Bookmarked

2

Total users

1

Monthly active users

3 hours ago

Last modified

Share

Veepee Scraper: Flash Sales, Prices, Discounts & Sizes

Veepee Scraper turns Veepee flash sales into clean structured data. Get every live campaign with its brand, sale dates, operation code and logos, plus per-sale items with price, was-price, discount percent, sizes and availability across France, Italy, Spain, Belgium and the Netherlands. Paste a sale link, monitor a market daily, or discover flashsales by keyword, then export to JSON, CSV or Excel, or pull the results straight into your app through the API.

Why This Scraper?

  • Two ways in, every link shape covered. List the live sales of a market with optional keyword checks, or paste sale ids and links: bare ids, catalog links, product pages and legacy redirect links all resolve, and a full link always uses its own storefront. No need to build URLs by hand.
  • Two record types, fully expanded. Campaigns carry brand, dates, operation code, sale type and logos; items carry price, was-price, discount percent, sizes, availability and deadlines.
  • Five markets. France, Italy, Spain, Belgium and the Netherlands each map to their own storefront host and catalog partition, verified live.
  • Sessions handled for you. Campaign discovery is anonymous and always works. Sale item detail rides on the member catalog API through a session the actor provisions itself: it reuses its cached session and automatically registers a fresh one whenever the saved one is rejected. You never paste cookies or credentials.
  • Built for schedules. Incremental mode returns only new and changed records on recurring runs, and a refused or session-blocked run fails loudly instead of returning an empty dataset.

Use Cases

  • Who: deal hunters and price trackers. What: watch flash-sale calendars per brand and get alerted when a new campaign opens or a price moves.
  • Who: fashion resale and arbitrage sellers. What: collect discount depth and size availability across sales to spot stock worth listing elsewhere.
  • Who: brand and retail analysts. What: track how often a brand appears, how long sales run, and how deep the markdowns go per market.
  • Who: affiliate and content teams. What: feed live sale cards with dates, brand art and links into newsletters or deal pages automatically.

Data You Get

Sample shape: values are illustrative placeholders, not from a live record.

FieldExample
type"campaign" (also "item")
id"campaign:897798"
saleId897798
brand"Eden Park"
operationCode"EPARK112"
beginDate / endDate"2026-10-05T05:00:00Z" / "2026-10-17T06:00:00Z"
saleTypeId1
saleUrlcampaign link on the market storefront
logo / logos / image / webImage / mobileImagebrand logos and campaign artwork for each device
brands / brandIdsall campaign brands and their identifiers
tagline / categoryIdshort sale description and campaign categories
saleBusinessId / saleSectorId / saleSubSectorId / businessUnit / isBrandAlert / isShareable / isNewCatalog / isPreopeningsale classification identifiers and flags
itemId"ABC123" (item rows)
name"Polo pique homme" (item rows)
price / wasPrice / discountPct39.99 / 89.0 / 55.1 (item rows)
sizes / variants["S", "M", "L"] (item rows)
comparisonPriceDescription / paymentOptionscomparison-price explanation and available payment options
images / thumb / description / datasheetUrl / sizeGuideUrlproduct artwork, description and information links, when available
availability / deadline"in_stock" / sale end date (item rows)
market"fr"
urlstorefront link to the sale or item

Item rows are scoped to what the authenticated catalog API returns: price, was-price, discount, sizes or variants, availability and deadlines.

How to Use

  1. Pick a mode (defaults to search): search (live sales for a market, optional keyword check) or urls (paste sale ids or links).
  2. Pick the market (search mode lists this country's live sales; bare sale ids use it too; full links carry their own storefront).
  3. Set Max items to control run size and cost, then click Start.
  4. Download the dataset as JSON, CSV or Excel, or read it through the API.

Live sales in France (no keywords):

{
"mode": "search",
"market": "fr",
"maxItems": 50
}

Items of one sale by id (session handled automatically):

{
"mode": "urls",
"market": "fr",
"urls": ["901048"],
"maxItems": 50
}

Paste links (ids, catalog pages, product pages and legacy redirects all resolve):

{
"mode": "urls",
"urls": ["https://www.veepee.fr/gr/catalog/901048", "https://www.veepee.fr/gr/product/901048/102086655"]
}

Live sales plus a keyword check:

{
"mode": "search",
"market": "fr",
"searchQueries": ["Nike"],
"maxItems": 20
}

Run it from your code

Python:

from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("abotapi/veepee-scraper").call(run_input={"mode": "search", "market": "fr"})
for sale in client.dataset(run["defaultDatasetId"]).iterate_items():
print(sale["brand"], sale["beginDate"], sale["saleUrl"])

JavaScript:

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('abotapi/veepee-scraper').call({ mode: 'search', market: 'fr' });
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Or connect it to Make, Zapier, n8n, Google Sheets or webhooks from the Integrations tab.

Automatic member session (sale item detail)

Sale item detail lives behind the member catalog API, which answers 401 without a session. The actor handles this entirely on its own: it reuses its sealed, encrypted per-market session when one is cached, and otherwise registers a fresh member automatically. If a saved session is ever rejected, at run start or while reading a sale, the actor registers a brand-new one in the same run and retries the refused sales, so a blocked session never fails your run. Campaign discovery never touches this lane. If registration itself is refused (rare), sale-scoped runs still return the anonymous campaign rows and say so clearly instead of returning a silent empty dataset.

Resume and recurring updates

  • Resume (resumeFromRunId) continues one interrupted run: paste its run or dataset ID and the actor skips everything already collected there, so you don't pay twice.
  • Incremental mode (incrementalMode) is for scheduled runs over the same scope. Each record is classified NEW, UPDATED (with changedFields), UNCHANGED (suppressed and not billed unless emitUnchanged is on), REAPPEARED or EXPIRED (only after a run that scanned the whole scope, and only with emitExpired). stateKey names or shares the stored state. With incremental mode off, output is exactly as before.

Send results into your apps (MCP connectors)

Optionally pipe the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step after the scrape: the Apify dataset is never changed.

What gets written to the connector: a condensed, human-readable summary of each record, not the full JSON. Each item becomes one entry with a title and its key fields flattened to plain text. The complete record always stays in the Apify dataset.

  1. Authorize a connector once under Apify → Settings → Integrations (Notion, Linear, Airtable, or Apify).
  2. Select it in the "Pipe results into your apps" input field. (If the picker is empty, you haven't authorized a connector yet.)
  3. For Notion, also set notionParentPageUrl to the page where items should be created.

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip.

Input Parameters

ParameterTypeDefaultDescription
modestringsearchsearch (live sales + keyword check) or urls (paste sale ids or links).
marketstringfrfr, it, es, de, be, lu, nl, uk, pt. Full links carry their own storefront.
urlsarray["901048", ...]Sale ids or Veepee links (urls mode).
searchQueriesarray(none)Optional keywords for the suggestions check (search mode).
includeItemsbooleantrueFetch per-sale item rows (session handled automatically).
includeItemDetailsbooleanfalseExtra per-item options and price fetch (bills item-enrichment).
maxItemsinteger50Stop after this many records (0 = no limit).
maxConcurrencyinteger3Parallel requests, 1 to 5.
requestDelaySecsnumber0.5Pause between fetches.
resumeFromRunIdstring(none)Continue one interrupted run.
incrementalModebooleanfalseReturn only new and changed records on scheduled runs.
stateKeystring(none)Name or share an incremental-mode state.
emitUnchangedbooleanfalseAlso return (and bill) unchanged records.
emitExpiredbooleanfalseAlso return (and bill) expired records.
ignoreFieldsForChangesarray(none)Fields that never mark a record UPDATED.
proxyobjectApify ProxyConnection settings.
mcpConnectorsarray(none)Optional: send a summary of each record to apps you authorized under Integrations.
notionParentPageUrlstring(none)Notion connector only: page under which records are created.
maxNotifyListingsinteger50Cap on items written to each connector per run.

Output Example

Sample shape: values are illustrative placeholders, not from a live record.

Campaign row (item rows share the same envelope):

{
"type": "campaign",
"id": "campaign:897798",
"saleId": 897798,
"brand": "Eden Park",
"operationCode": "EPARK112",
"beginDate": "2026-10-05T05:00:00Z",
"endDate": "2026-10-17T06:00:00Z",
"saleTypeId": 1,
"saleUrl": "https://www.veepee.fr/gr/catalog/897798",
"logo": "https://media.veepee.com/v1/media/2c9291ec-23fc-4b59-8817-ce3fedd8093b",
"market": "fr",
"source": "veepee"
}

Item rows carry itemId, name, price, wasPrice, discountPct, sizes and availability on top of the same envelope; see Data You Get for the full field list.

Plan Requirement

The default proxy setting works out of the box, and the actor rotates connections automatically when one is refused. For large or frequent runs, the residential proxy group gives more headroom; pick it under Connection. If your Apify plan does not include proxy access, the run fails with a clear message instead of returning an empty result; a paid plan with proxy access is required.

FAQ

How much does it cost?

You pay per record returned: campaign and item rows bill the dataset-item event, with volume tiers down to a fraction of the list rate. Only includeItemDetails adds the small item-enrichment event, and only for items that needed the extra fetch. The Pricing tab shows the current rates. Use Max items to cap the cost of any run.

This actor collects campaign listings and catalog data through the site's own public and member APIs. You are responsible for how you use it: follow the site terms and the laws that apply to you, and get legal advice if you plan commercial redistribution. Prices and dates are generally facts, but brand names, logos and product photos may be subject to third-party rights. Item detail runs on a session the actor provisions itself; you never supply credentials.

Why does item detail need a session while live sales do not?

The live-sale listing and the search suggestions answer anonymously, so discovery always works with no credentials. The per-sale catalog API answers 401 without a member session; the actor registers and caches its own session automatically, so you never paste cookies or credentials, and a rejected session is re-registered and the refused sales retried within the same run.

Can I get only new or changed sales on a schedule?

Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Each run then returns only new and updated records, and unchanged ones are not billed.

Why did my sale run fail instead of returning an empty dataset?

If automatic session registration could not establish a session, the run stops with a clear message so "no session" is never confused with "sale has no items". The next run retries registration automatically; anonymous campaign rows are still returned when any could be read. If only some sales could be read, you still get what was found.

Can I use it with AI agents or MCP?

Yes. Call it from any Apify integration or MCP client, and use the connector field to push results into Notion, Linear or Airtable.

🔗 More scrapers you might like

Pair this actor with these related scrapers from the same team:

🥦 Auchan France Scraper
Scrape Auchan.fr products: grocery, drinks, household and general merchandise. Real price...
🛒 Castorama.fr
Scrape Castorama.fr DIY and home-improvement products by keyword, category, or URL...
💼 France Travail Scraper
Scrape job offers from France Travail with titles, companies, locations, salaries...
🏷️ Leboncoin FR
Pull public leboncoin.fr listings across cars, property, jobs, electronics, furniture...
🥦 E.Leclerc Scraper
Scrape E.Leclerc France (e.leclerc) grocery and retail products. Search by keyword or...
📇 PagesJaunes FR
From $0.8/1K. Scrapes business listings from PagesJaunes.fr (French Yellow Pages)...

👉 Browse all abotapi scrapers

💬 Support & custom scrapers

  • 🐞 Found a bug or a missing field? Open a ticket on the Issues tab. We usually reply within hours.
  • 🛠️ Need another site, extra fields or a private build? Email contact@abotapi.com or message Telegram @abotapi.
  • ⭐ Enjoying it? A quick review on the actor page helps other users find it.