Hagebau APIhagebau.de ↗
Access hagebau.de product catalog, category tree, brand listings, search results, and store finder via a structured REST API. 7 endpoints for German DIY data.
What is the Hagebau API?
The hagebau.de API exposes 7 endpoints covering the full product catalog of Germany's hagebau home improvement chain, including product search, hierarchical category browsing, brand aggregation, detailed product attributes, and store lookup. The get_product_details endpoint returns schema.org structured data, tracking metadata, and key-value feature attributes for any product URL, while search_products handles both keyword queries and category-redirect searches.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/ea4e589d-8a57-4950-9af3-d23a2af6a283/get_categories' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace hagebau-de-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.hagebau_api import Hagebau, Category, Product, Brand, Store
hagebau = Hagebau()
# Construct a category by its URL slug and browse its products
category = Category(_api=hagebau, url="auto-zweirad-autobatterien")
for product in category.products(limit=5):
print(product.name, product.sku, product.available)
# List brands in that category
for brand in category.brands():
print(brand.name, brand.count)
# Search for products across the catalog
for product in hagebau.products.search(query="bosch akkuschrauber", limit=3):
print(product.id, product.name, product.review_average)
# List all brands across the catalog
for brand in hagebau.brands.list_all(limit=10):
print(brand.name, brand.count)
# Find stores near Berlin
for store in hagebau.stores.find(query="Berlin"):
print(store.id, store.url)
Get the full hierarchical category tree from hagebau.de. Returns nested categories with IDs, URLs, product counts, and children. No parameters required.
No input parameters required.
{
"type": "object",
"fields": {
"id": "string - category ID",
"url": "string - category URL slug",
"name": "string - root category name",
"children": "array of nested category objects"
},
"sample": {
"data": {
"id": "237342220",
"url": "/connect-consolidated/",
"name": "Connect consolidated",
"level": 0,
"children": [
{
"id": "237594962",
"url": "/auto-zweirad/",
"name": "Auto & Zweirad",
"level": 1,
"children": [
{
"id": "237596188",
"url": "/auto-zweirad-autobatterien/",
"name": "Autobatterien",
"level": 2,
"hasChildren": true,
"totalProductCount": 85
}
],
"hasChildren": true,
"totalProductCount": 5243
}
],
"hasChildren": true
},
"status": "success"
}
}About the Hagebau API
Category and Product Browsing
The get_categories endpoint returns the complete hagebau.de category tree as nested objects, each with an id, url slug, name, totalProductCount, and a children array for subcategories. These slugs feed directly into get_category_products, which accepts a category_slug parameter and returns paginated product listings with name, price, id, images, brand, features, and url per product. Note that only level-2 or deeper slugs are valid for this endpoint — top-level slugs like garten or auto-zweirad return a 403 error from the source, so always use get_categories to discover valid deeper paths before querying products.
Search and Brand Data
search_products accepts a query string (e.g. 'bosch akkuschrauber') and an optional page integer for pagination. It returns a products array, a totalCount, and a filters object. The endpoint handles category-redirect cases where a single generic term maps to a category rather than a flat result set. get_category_brands returns brand names and per-brand product counts for a given level-2+ category slug, sourced from the manufacturer filter panel. get_all_brands aggregates brand data by sampling up to 10 level-2 subcategories — results are representative but not exhaustive across the full catalog.
Product Details and Store Finder
get_product_details accepts either a full hagebau.de product URL or a relative slug. It returns three distinct objects: dl_obj (analytics metadata including productName, productPrice, productManufacturer, and categoryPath), schema (schema.org Product data with name, brand, offers, description, and sku), and attributes (a key-value map of product-specific feature fields). get_store_availability returns store IDs and full store page URLs; an optional query string filters results by matching against store URLs, which typically encode city names like berlin or hamburg.
The Hagebau API is a managed, monitored endpoint for hagebau.de — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when hagebau.de changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official hagebau.de API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Building a product price tracker for German hardware and building materials using
search_productsandget_product_details - Cataloging hagebau's full SKU inventory by walking the category tree from
get_categoriesand paginatingget_category_products - Extracting structured product specifications via the
attributesfield inget_product_detailsfor comparison tools - Identifying which brands carry the most products in a specific subcategory using
get_category_brands - Mapping hagebau store locations by city using
get_store_availabilitywith a city-name query filter - Aggregating brand presence across the hagebau catalog with
get_all_brandsfor competitive market research - Populating a product feed with schema.org data (name, SKU, offers, description) from
get_product_detailsfor structured data pipelines
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does hagebau.de have an official developer API?+
Why do some category slugs return errors in `get_category_products`?+
get_category_products. Top-level slugs such as garten or werkzeug are not valid inputs and will fail. Use get_categories first to retrieve the full nested tree, then use a child slug like werkzeug-maschinenwerkzeug or auto-zweirad-autobatterien as your category_slug parameter.Does `get_product_details` return stock availability or inventory levels?+
How complete is the data from `get_all_brands`?+
get_category_brands with a targeted category slug instead.