# Snipes Scraper — Sneaker & Streetwear Prices (`studio-amba/snipes-scraper`) Actor

Scrape product data from snipes.com, Europe's sneaker and streetwear retailer. Extract names, brands, prices, discounts, sizes, stock levels, and images via Snipes' own product search API. Covers Germany, France, Netherlands and Italy.

- **URL**: https://apify.com/studio-amba/snipes-scraper.md
- **Developed by:** [Studio Amba](https://apify.com/studio-amba) (community)
- **Categories:** E-commerce
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 result scrapeds

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

## Snipes Scraper

Pull product data from snipes.com, Europe's sneaker and streetwear retailer with stores across Germany, France, the Netherlands, Italy and beyond. This scraper pulls directly from Snipes' own product search API, so it returns clean, structured data -- brand, price, discount, per-size stock, images -- without any HTML parsing.

### How to scrape Snipes data

Give the actor a search term and a country and it queries Snipes' search endpoint directly, paginating until it hits `maxResults` or runs out of matching products. There's nothing to configure beyond the search term and country -- no category URLs to hunt down, no pagination logic to babysit.

Under the hood, Snipes' storefront (built on the SCAYLE headless-commerce platform, the same platform behind Deichmann and Ochsner Sport) calls an unauthenticated JSON API at `api.snipes.com` for every search and category browse. This actor talks to that same API directly instead of rendering pages and parsing HTML, which makes it faster and far less likely to break when Snipes tweaks its frontend markup.

If you don't provide any input, it defaults to searching for `"sneaker"` in Germany as a demo.

### Input

| Field | Type | Description |
|-------|------|-------------|
| `searchQuery` | string | Search term, in the language of the selected country (e.g. `"sneaker"` for DE/NL/IT, `"baskets"` for FR) |
| `country` | string | Storefront to scrape: `DE`, `FR`, `NL` or `IT` (default: `DE`) |
| `maxResults` | integer | Cap on number of products returned (default: 100) |
| `proxyConfiguration` | object | Apify proxy settings. Snipes' product API has no anti-bot protection, so the default Apify proxy is sufficient -- no residential proxy needed |

### What you get back

| Field | Type | Example |
|-------|------|---------|
| `name` | string | `"adidas Originals Stan Smith Sneaker weiß"` |
| `brand` | string | `"adidas Originals"` |
| `price` | number | `109.99` |
| `originalPrice` | number | null | `121.99` (only set when the item is discounted) |
| `currency` | string | `"EUR"` |
| `discount` | string | null | `"-18%"` |
| `sku` | string | `"01331729"` |
| `productId` | string | `"m02221730"` |
| `inStock` | boolean | null | `true` (null only if the source omits stock data) |
| `stockLevel` | integer | null | `330` (total units across all sizes) |
| `url` | string | Full product page URL |
| `imageUrl` | string | Primary product image |
| `imageUrls` | array | All product images |
| `category` | string | null | Most specific category label the API exposes |
| `country` | string | Storefront country scraped (`DE`, `FR`, `NL` or `IT`) |
| `sizes` | array | Per-size stock: `[{"size": "41", "inStock": true, "stockQuantity": 14}]` |
| `scrapedAt` | string | ISO timestamp |

### Sample output

```json
{
  "name": "Nike Hakimi / No. 2 / PSG Nike Third Stadium 2025/26 rot",
  "brand": "Nike",
  "price": 100,
  "originalPrice": 121.99,
  "currency": "EUR",
  "discount": "-18%",
  "sku": "02573630",
  "productId": "m02490210",
  "inStock": true,
  "stockLevel": 42,
  "url": "https://www.snipes.com/de-de/p/nike-hakimi-no-2-psg-nike-third-stadium-2025-26-rot-102345",
  "imageUrl": "https://asset.snipes.com/images/f_auto,q_auto,w_800/02573630_1/img",
  "imageUrls": [
    "https://asset.snipes.com/images/f_auto,q_auto,w_800/02573630_1/img",
    "https://asset.snipes.com/images/f_auto,q_auto,w_800/02573630_2/img"
  ],
  "category": "Trikot",
  "country": "DE",
  "sizes": [
    { "size": "L", "inStock": true, "stockQuantity": 12 }
  ],
  "scrapedAt": "2026-08-24T19:48:20.780Z"
}
```

### Use cases

- **Price monitoring** -- track Snipes' own price and discount changes over time on the brands and styles you sell against.
- **Stock tracking** -- `sizes` gives you per-size availability, useful for spotting which sizes sell out fastest on drop-heavy sneaker releases.
- **Assortment research** -- see which brands and product lines Snipes is pushing, and at what price points, across four European markets.
- **Cross-market comparison** -- run the same search across `DE`, `FR`, `NL` and `IT` to compare pricing and assortment for the same sneaker or streetwear item across countries.

### Coverage

v1 covers four of Snipes' 12 country storefronts: Germany (`de-de`), France (`fr-fr`), the Netherlands (`nl-nl`) and Italy (`it-it`) -- Snipes' largest markets. Austria, Switzerland, Belgium, Spain, Poland, Portugal, Croatia and the smaller French/Dutch/German-Swiss/Austrian sub-locales aren't covered yet.

### Performance and cost

The scraper hits Snipes' JSON API directly -- no browser rendering, no HTML parsing -- so it's fast. A run of 100 products typically completes in well under 10 seconds and uses a fraction of a compute unit. You're billed per actor start plus per result scraped; check the current per-event pricing on this actor's page before running at scale. Your run's usage cost only settles after the run reports SUCCEEDED -- checking cost mid-run will undercount it.

### Limitations

- Four country locales in v1 (`DE`, `FR`, `NL`, `IT`). The other eight Snipes locales aren't covered yet.
- Ratings and review counts aren't exposed by the search API, so they're not included in the output.
- The search endpoint returns one representative variant per product, not the full size range -- `sizes` reflects that single sampled variant, not every size Snipes stocks.
- The API's `X-Charybdis` header (a shop-configuration blob, one per country) was harvested from a live browsing session per locale. It's static shop config, not a rotating secret, but if Snipes ever regenerates it for a locale, requests for that country will start failing until the actor is updated.
- Search is keyword-based, matching Snipes' own on-site search. It does not accept direct product or category URLs.

### Related scrapers

If you're covering European fashion and footwear retail more broadly, also check out:

- [Deichmann Scraper](https://apify.com/studio-amba/deichmann-scraper) -- German footwear, same SCAYLE platform family
- [Ochsner Sport Scraper](https://apify.com/studio-amba/ochsnersport-scraper) -- Swiss sporting goods, same SCAYLE platform family
- [C\&A Scraper](https://apify.com/studio-amba/c-and-a-scraper) -- European fashion retail, same corporate umbrella
- [Vinted Scraper](https://apify.com/studio-amba/vinted-scraper) -- European second-hand fashion marketplace

### Support

Found an issue or need a different locale covered? Open an issue on this actor's Apify Store page and we'll take a look.

# Actor input Schema

## `searchQuery` (type: `string`):

Search term to find products on snipes.com, in the language of the selected country (e.g. "sneaker" for DE/NL/IT, "baskets" for FR)

## `country` (type: `string`):

Snipes storefront to scrape. Each country has its own currency-neutral EUR pricing and catalog.

## `maxResults` (type: `integer`):

Maximum number of products to scrape

## `proxyConfiguration` (type: `object`):

Apify proxy configuration. Snipes' product API has no anti-bot protection (verified live), so the default Apify proxy is sufficient.

## Actor input object example

```json
{
  "searchQuery": "sneaker",
  "country": "DE",
  "maxResults": 100,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (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 = {
    "searchQuery": "sneaker",
    "country": "DE",
    "maxResults": 100,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("studio-amba/snipes-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 = {
    "searchQuery": "sneaker",
    "country": "DE",
    "maxResults": 100,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("studio-amba/snipes-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 '{
  "searchQuery": "sneaker",
  "country": "DE",
  "maxResults": 100,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call studio-amba/snipes-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,studio-amba/snipes-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/oHmeaMkefuXOIbTGA/builds/RBHdirfq3Q92Bc3S7/openapi.json