OBI Germany Product Scraper

Extract OBI Germany products, prices, online availability, postcode availability, and store information as structured data. Use it for price monitoring, product research, local availability checks, catalogue enrichment, and retail market analysis.

This is an unofficial scraper and is not affiliated with, endorsed by, or operated by OBI.

What you can extract

• Product identity, name, brand, canonical URL, images, seller, and marketplace status.
• Online, regular, comparison, and HEY OBI loyalty price fields kept separate when publicly available.
• Delivery and pickup availability for requested German postcodes.
• Store details by public store number.
• Store discovery by postcode, city, state, service, or coordinates.

Supported modes

search

Search products by query. Optional controls include maxResults, maxPages, sponsored-result filtering, product detail enrichment, and postcode availability enrichment.

{
  "mode": "search",
  "query": "bohrmaschine",
  "maxResults": 20,
  "maxPages": 2,
  "includeSponsored": false
}

item

Get product details for one or more OBI article IDs or approved https://www.obi.de/p/... URLs.

{
  "mode": "item",
  "products": [{"articleId": "5188784"}]
}

availability

Check pickup and delivery availability for explicit products and German postcodes.

{
  "mode": "availability",
  "products": [{"articleId": "5188784"}],
  "postalCodes": ["10115"],
  "quantity": 1
}

store

Retrieve one store by its public OBI storeNumber.

{"mode": "store", "storeNumber": "374"}

stores

Find stores by location or service filters.

{"mode": "stores", "city": "Niesky", "maxStores": 20}

Output

Rows are written to the default Dataset with an explicit recordType such as product, availability, store, or error. Product rows keep seller, price, availability, identity, image, and source metadata in separate fields. Run totals, warnings, and request counts are available in the OUTPUT and REQUEST_LEDGER_SUMMARY records in the default key-value store.

You can export results as JSON, CSV, Excel, XML, RSS, or access them through the Apify API and integrations.

Proxy and access behavior

Direct HTTP is the default and is currently proven for all supported modes. Apify proxy settings and custom proxy URLs are supported for blocked or location-sensitive runs. Proxy credentials are redacted from logs and request summaries. Browser fallback is intentionally disabled.

Limits and data notes

• Prices and availability can change between requests and may depend on location or seller.
• storeNumber is the public input identifier; internal store IDs are returned only as metadata.
• HEY OBI loyalty prices are kept separate from regular and online prices.
• Opening hours are returned only when present in the confirmed public store source.
• Invalid individual products can produce structured error rows instead of discarding successful results.

Pricing

The current price is displayed by Apify before a run. Dataset-result billing, when enabled, applies only to rows written to the default Dataset; failed retries and key-value summaries are not separate Dataset results.