Retail pricing and availability monitoring
Use Adidas endpoints to turn retail pricing and availability monitoring into repeatable API requests with documented inputs and JSON responses.
Turn Adidas.com's public storefront into structured retail data — keyword product search or category browse with real pagination and sort options, full product detail per SKU (pricing, description, images, every purchasable size), and a store locator with per-store detail (hours, phone, in-store services), all as normalized JSON. Credential-free.
Search and browse Adidas products, get full product detail, and find nearby Adidas stores as structured JSON.
Endpoint families
5
Documented params
15
Examples
0
Live catalog snapshot
Active endpoints
5
Methods
GET
Required params
10
Schema refs
5
{
"platform": "Adidas",
"endpoint": "adidas-search",
"method": "GET",
"path": "/adidas/search",
"auth": "apiKey"
}Use cases
Search and browse Adidas products, get full product detail, and find nearby Adidas stores as structured JSON.
Use Adidas endpoints to turn retail pricing and availability monitoring into repeatable API requests with documented inputs and JSON responses.
Use Adidas endpoints to turn product catalog research into repeatable API requests with documented inputs and JSON responses.
Use Adidas endpoints to turn store locator and footprint mapping into repeatable API requests with documented inputs and JSON responses.
Managed execution
Each Crawlora platform API is designed around a specific data surface. Instead of exposing a generic fetch endpoint, Crawlora combines endpoint-specific request logic, managed infrastructure, parsing, normalization, billing, and Playground-tested examples.
Request behavior is tuned for the target platform and endpoint type.
Supported endpoints can use managed proxy routing to improve reliability and reduce infrastructure work.
Dynamic pages can be routed through managed browser instances where JavaScript rendering is required.
Challenge pages and unusable upstream responses are detected and surfaced clearly.
Results are returned as documented JSON instead of raw HTML.
Test the same route from Docs and Playground before production integration.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/adidas/product
/adidas/search
/adidas/store
/adidas/stores
/adidas/suggest
Endpoint catalog
/adidas/searchSearches Adidas.com product listings by keyword, or browses a category listing by taxonomy slug, with real pagination and sort options. Exactly one of query or category is required. Returns normalized product summaries (title, price, rating, images, color variants) plus facet filter groups, sort options, and (for category browse) a breadcrumb trail. Keyword search is best-effort relevance, not a guaranteed match: an obscure keyword returns whatever Adidas's own search index surfaces. A genuinely empty keyword search returns an empty product list, and requesting a page beyond the available result pages (or an unknown category) returns a not-found error. Category values are the path segment after /us/ in an Adidas category URL (e.g. women-athletic_sneakers); they can also be read from the url fields of a search/category response's own filters and breadcrumbs.
/adidas/productReturns normalized product-detail data for one Adidas SKU: name, brand, category, description, pricing (current/standard/sale), images, and every purchasable size variant. product_id is the Adidas SKU (e.g. JI0397), taken from a search result's products[].id field or the trailing segment of an Adidas product page URL. An unknown product_id returns a not-found error.
/adidas/suggestReturns the top matching products for a partial query, the same search-as-you-type preview Adidas's own search box shows. Adidas has no separate term-autocomplete index, so each suggestion is a matching product (id, title, url, image, price) rather than a completed search phrase. Best-effort relevance: an obscure query returns whatever Adidas's own search surfaces.
/adidas/storesReturns Adidas physical retail stores nearest to a coordinate, sourced from Adidas's own store-finder API: name, address, phone, coordinates, distance in miles, opening hours, and in-store feature flags. lat and lng are both required. Adidas's upstream ignores a caller-supplied radius and returns the nearest ~20 stores ordered by distance. A location with no stores returns an empty list rather than an error.
/adidas/storeReturns normalized detail for one Adidas retail store: name, status, phone, description, full address, coordinates, opening hours, and in-store services (e.g. Click and Collect, Free Wi-Fi). store_id is the numeric Adidas store id, taken from an adidas-stores response's stores[].id field. An unknown store_id returns a not-found error.
Related APIs
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.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.
How to scrape Adidas
Crawlora's Adidas endpoints return product search/browse, product detail, and store locator data as normalized JSON with one API key — no Adidas account required.
Send a keyword to /adidas/search, or a category taxonomy slug to browse a listing instead, both with real pagination and sort options — normalized product summaries, facet filters, and sort options.
Pass a product_id (SKU) from a search result's products[].id field to /adidas/product for pricing, description, images, and every purchasable size variant.
Pass lat/lng to /adidas/stores for the nearest Adidas retail stores, nearest-first, with hours, phone, and in-store service flags.
Pass a store_id from a /adidas/stores result to /adidas/store for that store's full detail — status, description, opening hours, and services.
Send a partial query to /adidas/suggest for the same search-as-you-type product preview Adidas's own search box shows.
FAQ
Send a keyword to Crawlora's /adidas/search endpoint and get normalized product summaries — pricing, sizes, color variants — as structured JSON, no Adidas account required.
Yes — pass a category taxonomy slug to /adidas/search instead of a query for the same paginated listing shape, including a breadcrumb trail.
Pass latitude and longitude to /adidas/stores for the nearest stores, each with its own distance, hours, phone, and in-store service flags.
No — an obscure query returns whatever Adidas's own search index surfaces as a best-effort relevance match, not a guaranteed match, the same caveat as other major retail search APIs.