# Knuspr.de Scraper — German Online Grocery Data (`studio-amba/knuspr-scraper`) Actor

Scrape grocery products, prices, stock, and categories from Knuspr.de, the German Rohlik Group store. Search or browse by category.

- **URL**: https://apify.com/studio-amba/knuspr-scraper.md
- **Developed by:** [Studio Amba](https://apify.com/studio-amba) (community)
- **Categories:** E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.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

## Knuspr.de Scraper - German Online Grocery Products & Prices

Extract grocery product data, prices, stock availability, and categories from [Knuspr.de](https://www.knuspr.de), the German online supermarket operated by Rohlik Group. Get clean, structured data in EUR, without login or cookies.

### What is Knuspr.de Scraper?

Knuspr.de Scraper collects structured product data from Knuspr.de, Germany's fast-growing online grocery platform. It uses Knuspr's internal REST API to extract product details, pricing, stock levels, and full category paths, so you get clean structured data without parsing unreliable HTML.

Knuspr.de is the German brand of Rohlik Group, Central Europe's fast-growing online grocery company (the same platform behind Rohlik.cz in the Czech Republic, Kifli.hu in Hungary, and Gurkerl.at in Austria). Knuspr serves the Munich metro area with a catalogue of thousands of fresh and packaged grocery products and fast delivery windows. That makes it one of the richest structured grocery data sources in Germany.

**Popular use cases:**

- **Grocery price monitoring** - Track prices across the German market. Detect promotions, seasonal pricing shifts, and price changes over time.
- **Competitor intelligence** - Compare Knuspr's product range and pricing against REWE, Edeka, Flink, and other German grocery delivery platforms.
- **Market research** - Analyze product availability, brand distribution, and category structure in the German online grocery segment.
- **Supply chain analysis** - Monitor stock levels and availability patterns to understand supply dynamics.
- **Food industry research** - Study product ranges, brand penetration, and pricing strategies in a fast-growing online grocery market.

### How to scrape Knuspr.de data

There are two ways to collect data: search by keyword, or browse a category. You can also leave the input empty and the actor returns a default set of products.

#### Option 1: Search by keyword

Set `searchQuery` to any product name or keyword in German. The actor queries Knuspr's search API and hydrates every matching product with full details.

**German examples:** `"milch"` (milk), `"brot"` (bread), `"butter"` (butter), `"hähnchenbrust"` (chicken breast), `"käse"` (cheese), `"apfel"` (apple)

#### Option 2: Browse by category

Set `categoryId` to a Knuspr category ID to page through an entire category. A category ID takes priority over a search query.

Find category IDs in category page URLs. For example `https://www.knuspr.de/c1-obst-gemuese` uses category ID `1`.

**Useful category IDs:**

- `1` - Obst & Gemüse (Fruit & Vegetables)
- `12` - Obst (Fruit)
- `16` - Bananen & Exoten (Bananas & Exotic Fruit)
- `2431` - Pflanzendrinks (Plant-based Drinks)
- `2430` - Pflanzenbasiertes Kühlregal (Plant-based Chilled)
- `13` - Äpfel & Birnen (Apples & Pears)

### Input parameters

| Field | Type | Description |
|-------|------|-------------|
| `searchQuery` | string | Product name or keyword in German (e.g. `"milch"`). Ignored if `categoryId` is set. Defaults to `"milch"` when nothing is provided. |
| `categoryId` | string | Knuspr category ID to browse (e.g. `"1"`). Takes priority over `searchQuery`. |
| `maxResults` | integer | Maximum number of products to return. Default `100`. Hard-capped at `100000` per run. |
| `proxyConfiguration` | object | Proxy settings. Apify Proxy (automatic) is used by default — no anti-bot protection was found on Knuspr.de. |

#### Example input

```json
{
  "searchQuery": "brot",
  "maxResults": 100,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

#### Example input - browse a category

```json
{
  "categoryId": "1",
  "maxResults": 500,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

### Output

Each product is a structured record. Prices are in euros (EUR).

```json
{
  "name": "Alpro Barista Haferdrink VEGAN",
  "brand": "Alpro",
  "price": 2.59,
  "currency": "EUR",
  "url": "https://www.knuspr.de/5498-alpro-barista-haferdrink-vegan",
  "productId": "5498",
  "inStock": true,
  "pricePerUnit": "2.59 EUR/l",
  "imageUrl": "https://cdn.knuspr.de/images/grocery/products/5498/5498-1715783372898.jpg",
  "category": "Haferdrink",
  "categories": ["Plant Based", "Pflanzenbasiertes Kühlregal", "Pflanzendrinks", "Haferdrink"],
  "textualAmount": "1 l",
  "scrapedAt": "2026-08-31T09:06:45.223Z"
}
```

#### Output fields

| Field | Description |
|-------|-------------|
| `name` | Product name |
| `brand` | Brand or manufacturer |
| `price` | Current selling price (EUR) |
| `currency` | Currency code (EUR) |
| `originalPrice` | Price before discount, when on sale |
| `pricePerUnit` | Price per kg / l / unit |
| `discount` | Discount label, when on sale |
| `inStock` | Whether the product is currently in stock. Null when stock data was unavailable for that product — never coerced to false. |
| `category` | Deepest product category |
| `categories` | Full category path |
| `productId` | Knuspr product ID |
| `imageUrl` | Primary product image URL |
| `imageUrls` | All product image URLs, when more than one |
| `url` | Full product page URL |
| `textualAmount` | Human-readable pack size |
| `countryOfOrigin` | Country of origin, when available |
| `scrapedAt` | ISO 8601 timestamp of collection |

### How it works

The actor talks to Knuspr.de's own REST API rather than scraping rendered HTML. For a category, it fetches the list of product IDs, then hydrates each ID with parallel calls for product details, prices, stock, and category paths, and merges them into one flat record. For a search query, it reads product IDs from Knuspr's own search-metadata endpoint and hydrates them the same way. This keeps output stable even when the website's front-end markup changes.

Knuspr.de is one of four sibling stores that run on the same Rohlik Group platform (alongside Rohlik.cz, Kifli.hu, and Gurkerl.at) — the underlying `/api/v1` endpoints are identical across all four, verified live before this actor was built.

### Proxy and reliability

Apify Proxy (automatic) is used by default. Live testing found no anti-bot protection on Knuspr.de — plain requests get clean 200 responses. No login and no cookies are required.

### Cost and usage

This actor runs on the Apify platform's usage-based pricing. Cost per result is low: all data comes from lightweight JSON API calls rather than rendering pages, so a typical run scraping 100 products completes in well under a minute and uses minimal compute. The run's usage cost only settles after the run status reaches SUCCEEDED — reading the dataset mid-run undercounts cost, so check the Runs tab after completion for the final figure.

### Tips

- Use German keywords for the best search results.
- A `categoryId` returns an entire category and is the most complete way to collect a full product range.
- Raise `maxResults` to collect deeper category pages; lower it for quick samples.
- `inStock` can be `null` if stock data wasn't returned for a specific product — treat `null` as "unknown", not "out of stock".

### Frequently asked questions

**Do I need an account or login?**
No. The actor uses public API endpoints. No login or cookies are needed.

**What currency are prices in?**
Euros (EUR).

**How many products can I scrape?**
Set `maxResults` as high as you need, up to 100,000 per run. Category browsing pages through the full catalogue of a category.

**Is search or category browsing better?**
Search is best for a specific keyword. Category browsing is best for collecting a complete product range.

**Does Knuspr.de block scrapers?**
No anti-bot protection was found during testing. The actor uses Apify's automatic proxy by default.

### Related Scrapers

- [Rohlik Scraper](https://apify.com/studio-amba/rohlik-scraper) - Sibling Rohlik Group store: Rohlik.cz (Czech Republic)
- [Kifli.hu Scraper](https://apify.com/studio-amba/kifli-hu-scraper) - Sibling Rohlik Group store: Kifli.hu (Hungary)
- [Tesco HU Scraper](https://apify.com/studio-amba/tesco-hu-scraper) - Tesco Hungary online groceries
- [Albert Heijn Scraper](https://apify.com/studio-amba/albert-heijn-scraper) - Dutch online grocery
- [Jumbo Scraper](https://apify.com/studio-amba/jumbo-scraper) - Dutch online grocery
- [Colruyt Scraper](https://apify.com/studio-amba/colruyt-scraper) - Belgian online grocery

***

Built by Studio AMBA. Reliable scrapers for European e-commerce and grocery data.

# Actor input Schema

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

Search for products by name or keyword. Use German terms for best results (e.g., 'milch' for milk, 'brot' for bread). Ignored if a Category ID is set.

## `categoryId` (type: `string`):

Knuspr.de category ID to browse (e.g., '1' for Obst & Gemüse / Fruit & Vegetables). Find IDs in category page URLs: /c{ID}-{slug}. Takes priority over Search Query.

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

Maximum number of products to return.

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

Proxy settings. Apify Proxy (automatic) works reliably — no anti-bot protection detected on Knuspr.de.

## Actor input object example

```json
{
  "searchQuery": "milch",
  "maxResults": 20,
  "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": "milch",
    "maxResults": 20,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

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

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

```

## MCP server setup

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