kfzteile24 Scraper — Car Parts, Prices & Stock

Scrape car parts from kfzteile24.de, one of Germany's largest independent car-parts retailers: product names, brands, prices, part numbers, stock status, discounts, and images by keyword search.

What is kfzteile24 Scraper?

kfzteile24.de sells millions of car parts across every major brake, filter, suspension, and engine category, and independently prices against Autodoc and the dealership network. This actor takes any search keyword and returns the full listing-page data set for every matching product: current price (VAT included), the manufacturer's recommended retail price (UVP) and discount percentage, brand, manufacturer part number, stock/delivery status, and product images.

• Price monitoring — Track kfzteile24 pricing and discount depth across brake, filter, suspension, and engine categories
• Catalog enrichment — Pull brand, part number, and image data to enrich a parts database or comparison listing
• Competitive benchmarking — Compare kfzteile24 against Autodoc, ATU, or dealership pricing for the same part numbers
• Assortment analysis — See which brands (ATE, Bosch, Brembo, f.becker_line, ...) kfzteile24 stocks per category
• Deal tracking — The UVP/discount fields make it easy to find the deepest current markdowns

What data does kfzteile24 Scraper extract?

• Product name — The part-type name as listed (e.g. "Bremsbelagsatz, Scheibenbremse")
• Brand — Parts manufacturer (ATE, BOSCH, Brembo, f.becker_line, ...)
• Price — Current selling price, VAT included (EUR)
• Original price (UVP) — Manufacturer's recommended retail price before discount
• Discount — Percentage off the UVP (e.g. "-64%")
• SKU — Manufacturer part number as printed (e.g. "13.0460-2785.2")
• Product ID — kfzteile24's internal article number (e.g. "1410-32583")
• Stock status — Whether the product is currently available to order
• Delivery info — Same-day dispatch / delivery timing text as shown on the listing
• Images — Main image plus every additional product photo
• Category & category path — The breadcrumb category the product was found under
• URL — The canonical kfzteile24.de product page

How to scrape kfzteile24.de data

1. Enter a search keyword in searchQuery — any German car-part term works: "Bremsbeläge" (brake pads), "Ölfilter" (oil filter), "Stoßdämpfer" (shock absorbers), "Zündkerze" (spark plug).
2. Set maxResults. The actor pages through the listing (10 products per page) until it reaches that count or runs out of matching products.
3. Run the actor and export the dataset as JSON, CSV, or Excel from the Apify Console or via API.

Advanced users can instead pass startUrls with specific kfzteile24.de category or listing URLs (e.g. https://www.kfzteile24.de/ersatzteile-verschleissteile/bremsanlage/bremsbelaege) to scrape a fixed category tree instead of a keyword search.

Input

Field	Type	Description
searchQuery	String	Car-part search term (default: Bremsbeläge)
startUrls	Array	Advanced: specific category/listing URLs instead of a keyword search
maxResults	Integer	Maximum number of products to return (default: 100)
proxyConfiguration	Object	Apify proxy settings (Residential DE recommended for larger runs)

Example input

{
    "searchQuery": "Bremsbeläge",
    "maxResults": 100
}

Output fields

Field	Type	Example
name	String	"Bremsbelagsatz, Scheibenbremse"
brand	String	"ATE"
price	Number	50.7
currency	String	"EUR"
originalPrice	Number	144.23
discount	String	"-64%"
sku	String	"13.0460-2785.2"
productId	String	"1410-32583"
inStock	Boolean	true
deliveryInfo	String	"VERSAND HEUTE Sofort lieferbar"
imageUrl	String	image URL
imageUrls	Array	all product image URLs
category	String	"Bremsbeläge"
categories	Array	full breadcrumb path
url	String	product page URL
scrapedAt	String	ISO timestamp

Example output

{
    "name": "Bremsbelagsatz, Scheibenbremse",
    "brand": "ATE",
    "price": 50.7,
    "currency": "EUR",
    "url": "https://www.kfzteile24.de/artikeldetails?search=1410-32583",
    "scrapedAt": "2026-07-26T14:28:51.544Z",
    "originalPrice": 144.23,
    "discount": "-64%",
    "sku": "13.0460-2785.2",
    "productId": "1410-32583",
    "inStock": true,
    "deliveryInfo": "VERSAND HEUTE Sofort lieferbar",
    "imageUrl": "https://static.kfzteile24.de/product-images/ATE/K24-20260526.220504.272.f329c9cd.8086bad99f45cbce8d786bf6adfebbaffe811fe1.000651150.jpg",
    "imageUrls": [
        "https://static.kfzteile24.de/product-images/ATE/K24-20260526.220504.272.f329c9cd.8086bad99f45cbce8d786bf6adfebbaffe811fe1.000651150.jpg",
        "https://static.kfzteile24.de/product-images/ATE/K24-20260526.220504.284.50d9dbb5.8929fde4f58b1922eed76b41d6909bdce5ca70c9.000651150.jpg"
    ],
    "category": "Bremsbeläge",
    "categories": [
        "Ersatzteile | Verschleißteile",
        "Bremsanlage",
        "Bremsbeläge",
        "Bremsbelagsatz, Scheibenbremse"
    ]
}

How many results per run?

The listing page returns exactly 10 products per page (verified during build — the site clamps to 10 regardless of any page-size query override), and each page is a single lightweight HTTP request. A 100-product run finishes in well under a minute; a 1,000-product run takes a few minutes. There is no per-product detail-page fetch — every field above comes straight off the listing page, so run time scales with page count, not product count.

Why no product-detail-page data (EAN, full spec tables, ratings)?

kfzteile24.de's product detail pages (/artikeldetails) sit behind an AWS WAF Bot Control JavaScript challenge — confirmed during build via a direct HTTP request returning x-amzn-waf-action: challenge with an empty body. Plain HTTP/Cheerio requests cannot pass that challenge, so this actor never attempts to fetch detail pages. Everything it returns comes from the listing page itself, which the site serves as plain, unprotected server-rendered HTML (confirmed via direct curl with no cookies or session state) — including a structured GA4 ecommerce data block per product that this actor reads directly, alongside the surrounding price/stock/image markup. That covers name, brand, price, UVP, discount, part number, stock, and images reliably; it does not cover EAN codes, full technical spec tables, or customer ratings, which only appear on the challenge-gated detail pages.

Multi-country / multi-category use

kfzteile24.de is Germany-only (no other country storefronts), but the catalog spans every vehicle system. Useful searchQuery examples beyond brake parts:

{ "searchQuery": "Ölfilter" }
{ "searchQuery": "Stoßdämpfer" }
{ "searchQuery": "Zündkerze" }
{ "searchQuery": "Luftfilter" }

Limitations

• Germany only. kfzteile24.de has no other country storefronts.
• No EAN, full spec tables, or ratings. These only appear on the AWS-WAF-challenged detail pages (see above); the listing page does not expose them.
• Product name is the part-type name, not a unique title. The site itself labels every tile in a result set with the same generic part-type name (e.g. "Bremsbelagsatz, Scheibenbremse"); brand + sku are what distinguish individual products, exactly as the site's own catalog does.
• 10 products per page. This is a hard server-side ceiling — the actor compensates by paginating automatically, never by fetching detail pages.

Related Scrapers

• Autodoc Scraper — Car parts with OEM cross-reference numbers across ~27 European storefronts
• Reichelt Scraper — German electronics and components
• Euronics Scraper — German electronics retail

FAQ

Do I need a kfzteile24 account or cookies? No. Everything comes from public listing pages.

Can I search by part number instead of keyword? Yes — kfzteile24.de's search resolves manufacturer part numbers the same way it resolves keywords; put the part number in searchQuery.

Why do some categories return fewer results than requested? maxResults is capped by how many matching products the site actually has for that search term — the actor stops once it runs out, it never fabricates data.

Is scraping kfzteile24.de legal? This actor extracts publicly available listing-page data (prices, part numbers, stock status). You are responsible for how you use the data; check the terms that apply to your use case.