bike-discount.de APIbike-discount.de ↗
Access e-bike product listings, specs, motor details, geometry tables, pricing, and stock status from bike-discount.de via 9 structured endpoints.
curl -X GET 'https://api.parse.bot/scraper/4ceb9c0b-2187-44f1-a33c-0e32726674d0/get_ebike_category_listing?n=12&o=1&p=1' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve a paginated list of e-bikes from the category page. Returns product cards with name, price, URL, and image.
| Param | Type | Description |
|---|---|---|
| n | integer | Items per page. |
| o | integer | Sort order: 1=topseller, 2=price ascending, 3=price descending, 4=newest. |
| p | integer | Page number. |
{
"type": "object",
"fields": {
"page": "string page number requested",
"products": "array of product objects with name, brand, url, price_sale, price_uvp, image_url",
"total_on_page": "integer count of products returned on this page"
},
"sample": {
"data": {
"page": "1",
"products": [
{
"url": "https://www.bike-discount.de/de/rotwild-r.x750-pro",
"name": "Rotwild R.X750 PRO",
"brand": "",
"image_url": "https://www.bike-discount.de/media/e8/ac/b9/1756609756/rotwild-rx750f23ps1-20162745-r-x750-pro-1.jpg?ts=1756609756",
"price_uvp": "",
"price_sale": "UVP* 9.990,00 € 4.399,00 €"
}
],
"total_on_page": 48
},
"status": "success"
}
}About the bike-discount.de API
The Bike-Discount.de API provides access to e-bike product data across 9 endpoints, covering category listings, detailed technical specs, frame geometry, motor information, and pricing. The get_ebike_product_detail endpoint returns a full data set per product including specs, variants, geometry tables, and dataLayer metadata in a single call, while dedicated endpoints like get_ebike_specifications and get_ebike_motor_info isolate specific data types for lighter queries.
Browsing and Searching E-Bikes
The get_ebike_category_listing endpoint returns paginated product cards from the e-bike category, each with name, brand, url, price_sale, price_uvp, and image_url. Pagination is controlled via the p parameter, items per page via n, and sort order via o (1=topseller, 2=price ascending, 3=price descending, 4=newest). The search_products endpoint accepts a query string and returns the same card shape, echoing back the query and current page in the response. get_ebike_subcategories and get_brands_list return navigational data — subcategory names with URLs and brand names from the category filter — useful for building enumeration loops.
Product Detail and Specifications
All product-level endpoints accept a url_slug parameter formatted as a path starting with /de/ (e.g. /de/radon-render-10.0-750-2). get_ebike_product_detail is the most complete endpoint, returning name, brand, specs (a key-value object with labels like Rahmen, Motor, Akku), geometry (an array of tables, each table an array of row arrays), variants, motor_info, price_sale, price_uvp, and a dataLayer object containing structured metadata fields like productID, productPrice, and productCategory. If you only need specs, get_ebike_specifications returns just the specs object. get_ebike_motor_info returns only the motor_info string describing the drive system.
Pricing, Stock, and Geometry
get_ebike_pricing_and_stock returns price_sale, price_uvp, and the full dataLayer object, which includes productCurrency alongside pricing fields. This endpoint is the right choice when you need fresh price checks without pulling the full product detail. get_ebike_geometry returns the geometry array in isolation — geometry tables are not always present; when a product has no geometry data the array will be empty. Geometry rows are returned as arrays of arrays, so callers should handle variable table structures per product.
- Track sale price vs. UVP across brands using
price_saleandprice_uvpfrom category listings - Compare motor and drive system specs across models using
get_ebike_motor_infoand the Motor field inspecs - Build a frame geometry database for multiple e-bike models using
get_ebike_geometry - Monitor stock availability changes over time with periodic calls to
get_ebike_pricing_and_stock - Enumerate all brands and subcategories to systematically crawl the full catalog
- Power a product comparison tool using variant labels and spec key-value pairs from
get_ebike_product_detail - Feed a market analysis dashboard with structured
dataLayermetadata includingproductIDandproductCategory
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does bike-discount.de have an official developer API?+
What does the `dataLayer` object in `get_ebike_pricing_and_stock` actually contain?+
dataLayer object includes structured product metadata: productID, productPrice, productCurrency, and productCategory. These fields are returned alongside the human-readable price_sale and price_uvp strings, giving you both machine-readable and display-formatted pricing in the same response.Is geometry data always present in `get_ebike_geometry` responses?+
geometry field will be an empty array for products that don't list frame geometry. This is common for some urban and commuter e-bike models. Your code should handle both populated and empty geometry arrays.Does the API return user reviews or ratings for products?+
Can I filter category listings by brand or component spec?+
get_ebike_category_listing endpoint supports sort order via the o parameter and pagination via p and n, but does not accept brand or spec filter parameters directly. The get_brands_list and get_ebike_subcategories endpoints return navigational data you can use to construct targeted category URLs. You can fork this API on Parse and revise it to add brand or spec filtering as additional input parameters.