# reichelt Price Monitoring API

> Track reichelt.de component prices as JSON: price, stock status, delivery date, EAN and manufacturer part number per article – for BOM costing and alerts.

- URL: https://everydata.io/reichelt-price-monitoring-api
- Updated: 2026-10-28
- Publisher: everydata.io (https://everydata.io)

Electronics prices move quietly. A single-board computer can drop by thirty euros between two orders, a microcontroller module goes from "ab Lager" to a delivery date three months out, and the part on your bill of materials is suddenly the expensive line. The everydata.io reichelt Price Monitoring API is our product-details endpoint used on a schedule: every poll returns price, stock status, delivery time, EAN and manufacturer part number for an article on reichelt.de, and you keep the history.

## Key facts

- Platform: [reichelt Product Data API](https://everydata.io/apis/reichelt) (live)
- Main endpoint: `GET /rch/reichelt-lookup-product`
- Quota: A call to the reichelt API counts as 1 request against the monthly quota.
- Pricing: 100 free requests a month; paid plans from €30 a month for 5,000 requests (€1.00–€6.00 per 1,000 requests). One quota is shared across all 35 platforms; failed requests (5xx, blocked pages) are not counted.

## What you get

We do not store a reichelt price history for you. Each request is a live fetch of the product page, and your history is the table you write from the responses. What you store is what reichelt.de showed at the moment of the call, and you choose the cadence: weekly for a long BOM, daily for the handful of parts that decide whether a production run is affordable.

One observation holds the price in EUR as shown to a private customer in Germany, availabilityStatus with the shop's stock state (InStock, PreOrder, OutOfStock …) and deliveryMessage with the line reichelt prints next to it – "ab Lager, Lieferzeit: 1 - 2 Werktage", "Voraussichtlich lieferbar ab: 24.11.2026" or "z.Zt. ausverkauft". ean, mpn and the reichelt articleNumber identify the part, and productDetails carries the technical data grouped by section.

For whole product families, GET /rch/reichelt-search-by-keyword returns 16 tiles per page with price, availability, delivery line and article number, sorted by relevance or by price (price-asc, price-desc). One request shows every Raspberry Pi 5 variant or the cheapest ESP32 parts before you poll single articles.

- price as a number in EUR, including 19 % German VAT (private-customer view)
- availabilityStatus (InStock, PreOrder, OutOfStock …) and available as a boolean
- deliveryMessage with reichelt's delivery line, including the expected date for parts on order
- ean, mpn (manufacturer part number) and the reichelt articleNumber for BOM matching
- productDetails – technical data as name, value and group
- categories and categoriesExtended with the category path
- Search tiles sorted by price with price, availability and article number

## How it works

Store the product id (the number at the end of every reichelt product URL) for each part on your list and call GET /rch/reichelt-lookup-product with productId on a timer. A full product URL works as well. The example is the Raspberry Pi 5 with 8 GB RAM, polled on 28 October 2026.

```bash
curl -s "https://api.everydata.io/rch/reichelt-lookup-product?productId=359846" \
  -H "x-api-key: YOUR_API_KEY"
```

Response (shortened):

```json
{
  "responseStatus": "PRODUCT_FOUND_RESPONSE",
  "responseMessage": "Product successfully found!",
  "productTitle": "Raspberry Pi 5 B, 4x 2,4 GHz, 8 GB RAM, WLAN/ BT",
  "manufacturer": "RASPBERRY PI",
  "productId": "359846",
  "articleNumber": "RASP PI 5 B 8GB",
  "soldBy": "reichelt elektronik",
  "price": 189.99,
  "retailPrice": 0,
  "currency": "EUR",
  "available": true,
  "availabilityStatus": "InStock",
  "deliveryMessage": "ab Lager, Lieferzeit: 1 - 2 Werktage",
  "ean": "5056561803326",
  "mpn": "PI5 MODEL B/8GB",
  "categories": [
    "Entwicklerboards",
    "Einplatinen-Computer"
  ],
  "domainCode": "de"
}
```

The price series is the point. Our own catalogue example for this board, recorded a few weeks earlier, shows price 218.9; the poll above returned 189.99. reichelt shows no crossed-out reference price, so retailPrice is always 0 – a change in price between two polls is the signal, and only your stored history shows it.

Read availabilityStatus, not only available. available is true for every state in which reichelt accepts an order, including PreOrder: the 1 GB variant of the same board came back with available true, availabilityStatus PreOrder and deliveryMessage "Voraussichtlich lieferbar ab: 23.2.2027". The 16 GB variant was OutOfStock with "z.Zt. ausverkauft". For a BOM, "orderable but four months out" is usually a reason to look for a second source.

The price is the single-unit price for private customers, including 19 % VAT, as shown on the product page. Quantity breaks, prices for business customers and shipping costs are not part of the response. An unknown product id answers with HTTP 404 and is not billed, neither are errors on reichelt's side.

## What teams build with this

### BOM costing

Hardware teams keep the reichelt product ids of every part on a bill of materials and recalculate the board cost each week from price, so a price jump on one component shows up before the next order.

### Lead-time alerts

Poll availabilityStatus and deliveryMessage daily and alert when a part moves from InStock to PreOrder or OutOfStock, together with the expected delivery date reichelt prints.

### Second-source matching

Use mpn and ean to find the same component at other distributors and shops, and compare price and availability when reichelt runs out.

### Maker and board price tracking

Comparison sites and maker blogs track single-board computers, microcontroller kits and sensors across RAM and model variants with one search request per family, sorted by price.

### Catalogue enrichment

Shops and ERP systems fill EAN, manufacturer part number, category and technical data for components from productDetails instead of typing them from data sheets.

## Pricing

Each product poll is one request; a search page with 16 tiles is one request too. A BOM of 150 parts polled once a day is about 4,500 requests a month – the Starter plan (5,000 requests, €30). Daily polls of a full component catalogue of a thousand parts fit Production (50,000 requests, €80). Errors on reichelt's side are never billed.

## FAQ

### Does the API return a reichelt price history?

No. Every call is a live fetch of the current product page. Run the call on a schedule and store price, availabilityStatus and deliveryMessage with a timestamp – that table is your price history.

### Are quantity discounts or business prices included?

No. price is the single-unit price reichelt shows a private customer in Germany, including 19 % VAT. Quantity breaks, net prices for business accounts and shipping costs are not part of the response.

### Why is available true for a part that ships in months?

available is true for every state in which reichelt takes an order, including PreOrder and BackOrder. availabilityStatus gives the exact state and deliveryMessage the expected date, so use those for lead-time alerts.

### Can I look up a part by manufacturer part number?

Search with the part number as keyword via GET /rch/reichelt-search-by-keyword; the tiles return productId and articleNumber, and the product details return mpn and ean for an exact match.

### Are other reichelt countries supported?

The endpoints read reichelt.de in German with prices in EUR. Other country shops are not supported at the moment.

### Are reviews included?

No. reichelt shows no customer ratings, so countReview is 0 and productRating is null on every product.

## Related use cases

- [HORNBACH Price Monitoring API](https://everydata.io/hornbach-price-monitoring-api)
- [Kaufland Price Monitoring API](https://everydata.io/kaufland-price-monitoring-api)
- [Otto Price Monitoring API](https://everydata.io/otto-price-monitoring-api)
- [Amazon Price Tracker & Price History API](https://everydata.io/amazon-price-tracker-api)

## More

- [All platforms](https://everydata.io/apis) · [Pricing](https://everydata.io/pricing) · [API reference](https://everydata.io/docs) · [Getting started](https://everydata.io/docs/getting-started) · [MCP server](https://everydata.io/docs/mcp) · [Status](https://everydata.io/status)
- Machine-readable: [llms.txt](https://everydata.io/llms.txt), [llms-full.txt](https://everydata.io/llms-full.txt), [OpenAPI](https://api.everydata.io/openapi.json)