German retail catalog monitoring
Usa los endpoints de Otto para convertir german retail catalog monitoring en solicitudes API repetibles con inputs documentados y respuestas JSON.
Turn Otto.de — Germany's largest online retailer after Amazon — into structured JSON: keyword search, the top-level category tree, and full product detail including pricing and availability, all with one API key.
Search Otto.de's product catalog, browse its top-level categories, and get full public product detail as structured JSON.
Familias de endpoints
3
Parámetros documentados
6
Ejemplos
3
Snapshot en vivo del catálogo
Endpoints activos
3
Métodos
GET
Parámetros obligatorios
5
Referencias de esquema
3
{
"platform": "Otto",
"endpoint": "otto-search",
"method": "GET",
"path": "/otto/search",
"auth": "apiKey"
}Casos de uso
Search Otto.de's product catalog, browse its top-level categories, and get full public product detail as structured JSON.
Usa los endpoints de Otto para convertir german retail catalog monitoring en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Otto para convertir cross-category price and assortment tracking en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Otto para convertir search result research en solicitudes API repetibles con inputs documentados y respuestas JSON.
Ejecución gestionada
Cada cifra de abajo se lee directamente del catálogo de endpoints en vivo de Otto — 3 endpoints, 6 parámetros de solicitud documentados y 3 esquemas de respuesta publicados — el mismo catálogo contra el que corren Docs y Playground.
3 documented Otto endpoints, grouped into 3 request families — Categories, Product and Search.
6 request parameters are documented across those Otto endpoints, 5 of them required — the full input contract is public before you write any integration code.
3 of the 3 Otto endpoints ship a recorded example response, and 3 carry a documented response schema — you can code against the real JSON before the first request.
Otto endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
3 hosted MCP tools back the Otto endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Mapa de cobertura
/otto/categories
/otto/product
/otto/search
Catálogo de endpoints
/otto/searchSearches 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.
Herramienta MCP otto_search
/otto/categoriesLists the top-level categories shown in Otto.de's homepage navigation, each with its name and its canonical browse URL. The response also gives the `count` of categories and a `fetched_at` time. It takes no parameters.
Herramienta MCP otto_categories
/otto/productReturns a product's public detail, images, selectable colors and sizes. This endpoint uses a browser renderer because Otto.de product pages require JavaScript rendering.
Herramienta MCP otto_product
APIs relacionadas
Marketplaces & Retail
Research new, used, and vintage instruments across Reverb listings, seller shops, and the Price Guide. Keep current asking prices separate from historical sales, and preserve model, finish, year, condition, and currency when comparing gear.
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
Cómo hacer scraping de Otto
Crawlora's Otto endpoints return normalized public Otto.de storefront data as JSON with one API key — no Otto account required.
Call /otto/categories for Otto.de's top-level category directory — no parameters needed beyond the API key.
Send a required q keyword to /otto/search. The optional offset parameter pages through results in fixed 109-item increments (0, 109, 218, …) rather than a page number, matching Otto's own result-grid batching.
Pass a canonical Otto.de product URL — the kind /otto/search itself returns — to /otto/product for full detail. Otto.de sits behind a Kasada JS challenge, so this endpoint is served through Crawlora's browser-rendered fleet rather than a plain HTTP fetch.
Preguntas frecuentes
Call /otto/search with a keyword for results, /otto/categories for the top-level category tree, or /otto/product with a product URL for full detail — all return structured JSON with one API key.
The offset parameter advances in fixed 109-item increments (0 for the first page, 109 for the second, and so on) rather than a page number — pass Otto's own result-grid batch size back to move forward.
Otto.de's product pages sit behind a Kasada JavaScript challenge that blocks plain request-based and browser-impersonation transports, so this endpoint runs through Crawlora's CDP render fleet — the same tier as sites like Sephora.
No. All three endpoints read Otto's own public storefront and require only your Crawlora API key.