Kleinanzeigen Category Tree — Every Category ID & Parent
This is a fixed lookup: send an empty request and get back the Kleinanzeigen category tree as a flat list. Every department and subcategory comes with its ID, name, alias, URL and the ID of its parent.
{
"session_id": "11111111-1111-1111-1111-111111111111",
"kind": "kleinanzeigen_categories",
"human": "# Kleinanzeigen categories\n\n- **Records returned:** 161\n- **Proxy traffic:** 463.0 KB",
"machine": {
"total_items": 161,
"items": [
{
"id": "210",
"name": "Auto, Rad & Boot",
"alias": "auto-rad-boot",
"url": "https://www.kleinanzeigen.de/s-auto-rad-boot/c210",
"parent_id": null
},
{
"id": "216",
"name": "Autos",
"alias": "autos",
"url": "https://www.kleinanzeigen.de/s-autos/c216",
"parent_id": "210"
}
],
"proxy_traffic_bytes": 474063
},
"total_points": 5
}- You send
- Nothing — it's a fixed lookup
- You get back
- Every Kleinanzeigen category with ID, name, alias, URL and parent ID
- Coverage
- The Kleinanzeigen category tree.
- Price
- 5 points per run, flat — $5 per 1,000 runs
- Flat price per successful run. The request takes no input, so it either returns the tree or fails; there is no partial match to bill for.
Ways to get this data
Three approaches teams use today, and where each one runs into trouble.
| Approach | What it takes | Cost | Trade-off |
|---|---|---|---|
| Checking it by hand | Click through the site's departments and copy each category ID from the URL | Free, and tedious | Fine for a couple of categories, impractical for a full taxonomy |
| Building a scraper | Write it, host it, and repair it when the site's navigation changes | Engineering time | A maintenance commitment for something that isn't your product |
| NeuralVerge | One request, no parameters | $5 flat per run | Returns the whole tree every time; there is no way to ask for one branch |
What you get back
Every field in the response shown above.
| Field | Type | Description |
|---|---|---|
total_items | number | How many categories are in the list. |
items | array | The categories, as a flat list. |
id | string | Kleinanzeigen's ID for the category. This is the value to pass as category_id to listings search. |
name | string | Category name as shown on the site, in German. |
alias | string | URL-friendly slug for the category. |
url | string | Direct link to the category's page. |
parent_id | string | ID of the parent category; null for a top-level department. |
How to run it
The same lookup works from the app, the API, or as a tool an agent can call mid-task.
No parameters. Cache the response: the tree changes rarely, and the IDs are what you need to scope a listings search.
curl -X POST https://api.neuralverge.ai/functions/v1/run-kleinanzeigen-categories \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'What teams use it for
Where this field shows up in an actual workflow.
Look up the ID of a category once, then pass it as category_id to Kleinanzeigen listings search.
Use the parent_id links to rebuild the department and subcategory hierarchy in your own tool.
Match Kleinanzeigen categories to your own product taxonomy before comparing markets.
Coverage, freshness and limits
What this source covers, how fresh it is, and where it stops.
The Kleinanzeigen category tree.
Read at request time.
This source returns publicly visible category information, stamped with a session id you can trace.
- —The tree reflects the site's current categories; a category can be renamed or retired later.
- —There is no way to request a single branch; every call returns the whole list.
- —Names are in German, as the site publishes them.
Questions, answered
No. The request body is an empty object; this source takes no input.
Related sources
Search Kleinanzeigen ads by keyword, with category, price, condition, seller type, shipping and sort filters.
A single Kleinanzeigen ad by ID or URL: price, description, location, attributes, images and seller.
Amazon, eBay, Walmart, AliExpress and Alibaba product, seller and review data.
Try kleinanzeigen categories on your own data
One request format across every source in the catalog.