# Otto Scraper — German E-Commerce Products & Prices (`studio-amba/otto-scraper`) Actor

Scrape product data from otto.de. Extract names, prices, descriptions, images, and availability from Germany's #2 e-commerce platform.

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

## Pricing

from $2.00 / 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.

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

## Otto Scraper

Pull product data from otto.de, Germany's massive online department store. This scraper handles search queries and category pages across Otto's entire catalog -- furniture, fashion, electronics, home goods, and more.

### How it works

Paste in category URLs from otto.de. The scraper reads the listing pages (about 120 products per page, filled in through the same tile data feed the site itself uses) and, when `fetchDetails` is on, each product's own page. Pagination is handled automatically.

If you don't provide any input, it scrapes the bags category (https://www.otto.de/taschen/) as a demo.

**Search is unavailable since 2026-10-20.** otto.de blocks its search pages (`/suche/...`) for automated access with its Kasada bot protection. A run with a `searchQuery` or a `/suche/` URL fails within seconds with a message naming the block. Category URLs still work.

### Input

| Field | Type | Description |
|-------|------|-------------|
| `searchQuery` | string | Search otto.de for this term. Unavailable since 2026-10-20 (otto.de blocks search pages) |
| `categoryUrls` | array | Otto.de category or listing URLs to scrape |
| `maxResults` | integer | Cap on number of products returned (default: 100) |
| `proxyConfiguration` | object | Proxy settings -- recommended for larger runs |
| `fetchDetails` | boolean | Off by default. Fetch each product's own page for material, color, dimensions and other specs -- see [Product detail mode](#product-detail-mode) below |
| `maxDetailFetches` | integer | Cap on detail-page fetches per run when `fetchDetails` is on (default: 500) |

### What you get back

| Field | Type | Example |
|-------|------|---------|
| `name` | string | `"Ecksofa mit Schlaffunktion"` |
| `brand` | string | `"Home affaire"` |
| `price` | number | `449.99` |
| `originalPrice` | number | `699.99` |
| `currency` | string | `"EUR"` |
| `sku` | string | `"304815926"` |
| `inStock` | boolean | `true` |
| `rating` | number | `4.3` |
| `reviewCount` | number | `87` |
| `url` | string | Full product URL |
| `imageUrl` | string | Primary product image |
| `category` | string | `"Sofas & Couches"` |
| `scrapedAt` | string | ISO timestamp |

With `fetchDetails` on, each item also gets `attributes`, `material`, `color`, `dimensions`, `detailsFetched` and `detailUrl` -- see [Product detail mode](#product-detail-mode).

### Sample output

```json
{
    "name": "Ecksofa mit Schlaffunktion",
    "brand": "Home affaire",
    "price": 449.99,
    "originalPrice": 699.99,
    "currency": "EUR",
    "inStock": true,
    "rating": 4.3,
    "reviewCount": 87,
    "url": "https://www.otto.de/p/home-affaire-ecksofa-1234567/",
    "imageUrl": "https://i.otto.de/i/otto/product-image.jpg",
    "category": "Sofas & Couches",
    "scrapedAt": "2026-03-14T09:15:00.000Z"
}
```

### Product detail mode

Currently unavailable since 2026-09-29: otto.de blocks product pages, so runs with `fetchDetails` on return listing rows with `detailsFetched=false`. The option stays in the input so saved tasks keep working.

Off by default (`fetchDetails: false`). When available, it also pulls each product's own page for its full spec table -- material, color, dimensions, delivery notes and everything else Otto lists under "Details".

This costs one extra Bright Data request per product on top of the listing requests, because otto.de product pages sit behind Kasada anti-bot protection that a plain fetch can't get past. Bright Data Web Unlocker runs about $0.0015-0.003 per request, so a `fetchDetails` run roughly doubles Bright Data usage and takes noticeably longer than a listing-only run. `maxDetailFetches` (default 500) caps how many detail pages a single run will fetch, regardless of `maxResults`.

Each product detail page fetched is charged as a separate event, product-detail-fetch, at $0.004.

Current status (30 September 2026): otto.de is blocking its product pages for every access route we use, so detail fields come back empty. A run with `fetchDetails` on stops trying after the first three product pages fail and returns the listing data with `detailsFetched: false` within minutes. Failed detail fetches are not charged. Listing data (name, brand, price, rating, availability, image) is not affected.

Each item gets:

| Field | Type | Description |
|-------|------|-------------|
| `attributes` | object or null | Otto's spec tables, keyed by a slug of the German caption (`material`, `massangaben`, `farbe`, `ausstattung_funktionen`, ...), each an object of the site's original German key/value pairs |
| `material` | string or null | Flattened from the Material table's `Material`/`Bezug`/`Obermaterial` key |
| `color` | string or null | Flattened from the Farbe table's `Farbe` key |
| `dimensions` | object or null | `{breite, tiefe, hoehe}` in cm as numbers, parsed from the Maßangaben table |
| `detailsFetched` | boolean | True only when the detail page was fetched and attributes were parsed |
| `detailUrl` | string | The product page a detail fetch was (or would have been) attempted against |

Example input:

```json
{
    "categoryUrls": [{ "url": "https://www.otto.de/taschen/" }],
    "maxResults": 20,
    "fetchDetails": true,
    "maxDetailFetches": 20
}
```

A run's usage cost, including the extra Bright Data requests, only settles after the run reports SUCCEEDED -- reading the dataset mid-run undercounts what the run will actually cost.

### Typical costs

Around 1,000 products per $1 in Apify credits using CheerioCrawler. Proxy usage increases cost for large runs. With `fetchDetails` on, add roughly $0.0015-0.003 per product for the extra Bright Data request.

### Good to know

- All product data is in German
- Otto uses server-side rendering, so most data is accessible via HTTP
- The scraper follows product links matching `/p/` or `/produkt/` URL patterns
- Some pages may require proxy to avoid rate limiting on larger crawls

### How to scrape Otto data

1. Go to this actor's page on the [Apify Store](https://apify.com/store).
2. Click **Try for free** to open it in Apify Console.
3. Configure your search query or URL, set the maximum number of results, and adjust proxy settings if needed.
4. Click **Start** and wait for the run to finish.
5. Download your data in JSON, CSV, Excel, or connect it to your workflow via API.

You can also schedule regular runs, set up webhooks for real-time notifications, or integrate the results directly into your application using the [Apify API](https://docs.apify.com/api).

### Cost and performance

This actor charges $0.02 per run (start fee, based on its 4 GB memory allocation) plus $0.002 per result scraped. 100 results costs about $0.22; 1,000 results about $2.02. A run's usage cost only settles after it reports SUCCEEDED.

### Tips and tricks

- **Start small**: test with `maxResults: 5` before running large scrapes.
- **Use proxies**: residential proxies give the best success rates for Otto.
- **Schedule runs**: set up recurring runs to keep your data fresh automatically.
- **Integrate via API**: use the [Apify API](https://docs.apify.com/api) or [client libraries](https://docs.apify.com/api/client) to fetch results programmatically.
- **No login required**: this actor scrapes publicly available data without needing an account.

### Limitations

- Data is scraped from the public website and may change without notice.
- Some products or listings may not be available in all regions.
- Very large scraping jobs may be slower due to proxy rotation and rate limiting.
- Respect the website's terms of service and use responsibly.

### Features

- **No login required** — scrapes publicly available data from Otto without needing credentials or cookies.
- **Structured output** — results are returned as clean JSON objects, ready for processing.
- **Pagination handling** — automatically follows multiple pages of results.
- **Proxy support** — configurable proxy settings for reliable, large-scale scraping.
- **Flexible input** — search by keyword, provide specific URLs, or crawl categories.
- **Scheduled runs** — run on a schedule to keep your dataset up to date automatically.
- **API access** — integrate results into your workflow using the Apify API or webhooks.

### FAQ

**Is it legal to scrape Otto?**
Web scraping of publicly available data is generally permitted. This actor only accesses information that is publicly visible to any website visitor. Always review the website's terms of service before scraping.

**How often should I run this scraper?**
For price monitoring or competitive intelligence, daily or weekly runs are common. Set up a [schedule](https://docs.apify.com/schedules) in Apify Console to automate this.

**Can I export the data to Google Sheets or Excel?**
Yes. After each run, you can download results in CSV, JSON, or Excel format directly from Apify Console. You can also connect results to Google Sheets using Apify integrations.

**What if the scraper stops working?**
Websites change their structure occasionally. If you notice issues, please open an issue on the actor's page. We actively maintain this scraper and fix issues promptly.

# Actor input Schema

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

Search term to find products on otto.de. Unavailable since 2026-10-20: otto.de blocks search pages (/suche/) with its Kasada bot protection, so a search run fails with a message naming the block. Use categoryUrls instead.

## `categoryUrls` (type: `array`):

List of otto.de category URLs to scrape, for example https://www.otto.de/taschen/. Search URLs (/suche/...) are blocked by otto.de since 2026-10-20.

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

Maximum number of products to scrape

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

Apify proxy configuration

## `fetchDetails` (type: `boolean`):

Currently unavailable since 2026-09-29: otto.de blocks product pages, so runs return listing rows with detailsFetched=false. Intended to fetch each product's own page for material, color, dimensions and other specifications (attributes) in addition to the listing data. Off by default. Costs ONE EXTRA Bright Data request per product on top of the listing requests (~$0.0015-0.003 each) since otto.de product pages sit behind Kasada anti-bot protection, so turning this on roughly doubles the run's Bright Data usage and makes large runs take noticeably longer.

## `maxDetailFetches` (type: `integer`):

Hard cap on how many product detail pages this run will fetch when "Fetch product detail attributes" is on. Protects against accidentally launching thousands of extra Bright Data requests on a large maxResults run. Ignored when fetchDetails is off. Detail fetching is currently unavailable since 2026-09-29 (otto.de blocks product pages).

## `brightDataApiKey` (type: `string`):

Bright Data API key (Web Unlocker zone) used to reach otto.de product pages behind Kasada anti-bot protection. Only needed when "Fetch product detail attributes" is on. Falls back to the actor's own BRIGHT_DATA_API_KEY environment variable if left empty.

## Actor input object example

```json
{
  "categoryUrls": [
    {
      "url": "https://www.otto.de/taschen/"
    }
  ],
  "maxResults": 100,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "DE"
  },
  "fetchDetails": false,
  "maxDetailFetches": 500
}
```

# 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 = {
    "categoryUrls": [
        {
            "url": "https://www.otto.de/taschen/"
        }
    ],
    "maxResults": 100,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "DE"
    },
    "fetchDetails": false,
    "maxDetailFetches": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("studio-amba/otto-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 = {
    "categoryUrls": [{ "url": "https://www.otto.de/taschen/" }],
    "maxResults": 100,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "DE",
    },
    "fetchDetails": False,
    "maxDetailFetches": 500,
}

# Run the Actor and wait for it to finish
run = client.actor("studio-amba/otto-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 '{
  "categoryUrls": [
    {
      "url": "https://www.otto.de/taschen/"
    }
  ],
  "maxResults": 100,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "DE"
  },
  "fetchDetails": false,
  "maxDetailFetches": 500
}' |
apify call studio-amba/otto-scraper --silent --output-dataset

```

## MCP server setup

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