# Aldi Germany Scraper — aldi.de Product Prices (`noahadler/aldi-de-products`) Actor

Scrape ALDI SÜD Germany (aldi-sued.de) shelf prices: title, brand, EUR price, unit price when shown, category, product URL and image. Germany only — not UK/IE. HTTP JSON + RESIDENTIAL DE. PPE per product.

- **URL**: https://apify.com/noahadler/aldi-de-products.md
- **Developed by:** [Noah Adler](https://apify.com/noahadler) (community)
- **Categories:** E-commerce, Lead generation
- **Stats:** 2 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.21 / 1,000 products

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Aldi Germany Scraper — aldi.de Product Prices

**Aldi Germany scraper** for **ALDI SÜD** shelf prices on [aldi-sued.de](https://www.aldi-sued.de): title, brand, EUR price, unit price when shown, category, product URL and image.

**Scope: Germany only.** This Actor does **not** scrape Aldi UK (`aldi.co.uk`) or Ireland (`aldi.ie`) — those sites prohibit automated data collection in their terms. Do not use this Actor for UK/IE.

HTTP-only against the public `api.aldi-sued.de` product-search JSON. No login. No Playwright.

> **Proxy:** RESIDENTIAL **DE** by default. Without a German residential IP the API often returns Akamai 403.

**Keywords:** aldi scraper · aldi germany · aldi.de · aldi süd · aldi sued products · grocery prices germany

***

### What it does

| Step | Action |
|------|--------|
| 1 | Input: German `query` (optional) + `maxItems` + RESIDENTIAL DE |
| 2 | Calls `GET /v3/product-search` with `serviceType=walk-in` + store `servicePoint` |
| 3 | Normalizes SKU, title, brand, EUR price, unit-price display, category, URL |
| 4 | Pushes one dataset row per product (PPE) |

***

### Input

| Field | Required | Description |
|-------|----------|-------------|
| `query` | No | German keyword (`milch`, `kaffee`). Empty = catalog page |
| `categoryKey` | No | Optional category tree key |
| `servicePoint` | No | Store id (default `B384`) |
| `maxItems` | No | 1–500 (default 40) |
| `proxyConfiguration` | Recommended | RESIDENTIAL DE |

#### Try it example

```json
{
  "query": "milch",
  "maxItems": 20,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "DE"
  }
}
```

***

### Output example

```json
{
  "sku": "000000000330654001",
  "title": "Frische Vollmilch 3,5 % 1 l",
  "brand": "MILSANI",
  "price": 0.95,
  "priceDisplay": "0,95 €",
  "unitPriceDisplay": null,
  "currency": "EUR",
  "sellingSize": null,
  "category": "Milchprodukte & Eier",
  "url": "https://www.aldi-sued.de/produkt/milsani-frische-vollmilch-3-5-1-l-000000000330654001",
  "imageUrl": "https://dm.emea.cms.aldi.cx/is/image/…",
  "country": "DE",
  "market": "aldi-sued",
  "error": false
}
```

`unitPriceDisplay` and `sellingSize` are filled when ALDI shows them (~75 % in probes); they are not guaranteed on every SKU.

***

### Notes

- Not affiliated with ALDI. Descriptive use of the brand name only; custom Store icon (not the official logo).
- Prices are national catalog shelf prices for ALDI SÜD Germany, not store-stock availability.
- Soft-fail: one dataset row with `error=true` and an actionable message if Akamai blocks.

# Actor input Schema

## `query` (type: `string`):

German free-text search on aldi-sued.de (e.g. milch, kaffee, pasta). Leave empty for an unfiltered catalog page. Does not search UK/IE sites.

## `categoryKey` (type: `string`):

Optional ALDI SÜD categoryKey from the product-category-tree API. When set, restricts results to that category.

## `servicePoint` (type: `string`):

ALDI SÜD store id (e.g. B384). Catalog prices are national; the API still requires a valid servicePoint.

## `maxItems` (type: `integer`):

Maximum product rows (1–500).

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

api.aldi-sued.de sits behind Akamai. Use Apify RESIDENTIAL with country DE.

## Actor input object example

```json
{
  "query": "milch",
  "servicePoint": "B384",
  "maxItems": 40,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "DE"
  }
}
```

# Actor output Schema

## `products` (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 = {
    "query": "milch"
};

// Run the Actor and wait for it to finish
const run = await client.actor("noahadler/aldi-de-products").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 = { "query": "milch" }

# Run the Actor and wait for it to finish
run = client.actor("noahadler/aldi-de-products").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 '{
  "query": "milch"
}' |
apify call noahadler/aldi-de-products --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,noahadler/aldi-de-products"
        }
    }
}
```

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/qBpMRjySCe3FYlJPw/builds/eVVHGaiLpvoy9lNqC/openapi.json