/otto/categoriesapiKey3 credits/requestGet Otto.de's top-level categories
Returns the public top-level category navigation from Otto.de's server-rendered homepage. Each entry includes its canonical browsing URL.
Required params: None
API Reference
Use Crawlora's Otto API endpoints to extract supported public Otto data as structured JSON. This documentation covers 3 active endpoints including Get Otto.de's top-level categories, Get an Otto.de product, Search Otto.de products. Developers can use these endpoints for monitoring, enrichment, research dashboards, internal data pipelines, and agent-native workflows without maintaining platform-specific scraping code. Each endpoint page documents authentication, request parameters such as url, q, cURL examples, response examples, response schemas, errors, credit cost, and Playground testing. Send requests to the Crawlora API with an x-api-key header, review usage and plan limits on pricing, and test safe sample requests in Playground before moving the workflow into production.
Choose an endpoint, send an authenticated request with the x-api-key header, and inspect the normalized JSON response. The examples below use the public Crawlora API base URL and the same endpoint catalog used by Playground.
curl -X GET "https://api.crawlora.net/api/v1/otto/search?q=coffee" \
-H "x-api-key: $CRAWLORA_API_KEY"These endpoint cards are generated from the active Crawlora endpoint catalog, including method, path, auth mode, credit cost, parameter summary, docs, and Playground links.
/otto/categoriesapiKey3 credits/requestReturns the public top-level category navigation from Otto.de's server-rendered homepage. Each entry includes its canonical browsing URL.
Required params: None
/otto/productapiKey5 credits/requestReturns a product's public detail, images, selectable colors and sizes. This endpoint uses a browser renderer because Otto.de product pages require JavaScript rendering.
Required params: url:query
/otto/searchapiKey3 credits/requestSearches Otto.de's public catalogue and returns the server-rendered product cards. offset advances by Otto's fixed 109-card page size; valid values are 0, 109, 218, and so on.
Required params: q:query
| Endpoint | API path | Method | Credits | Required params | Docs | Playground |
|---|---|---|---|---|---|---|
| Get Otto.de's top-level categories | /otto/categories | GET | 3 credits/request | None | View docs | Try endpoint |
| Get an Otto.de product | /otto/product | GET | 5 credits/request | url:query | View docs | Try endpoint |
| Search Otto.de products | /otto/search | GET | 3 credits/request | q:query | View docs | Try endpoint |