Adidas APIadidas.cl ↗
Fetch Adidas Chile product listings and details via API. Filter by gender, sport, and category. Returns pricing, sizes, colors, images, and attributes.
What is the Adidas API?
The Adidas Chile API gives developers structured access to the adidas.cl product catalog through 2 endpoints. Use get_products to retrieve paginated listings filtered by gender, sport, or product type, and get_product_details to pull complete data on specific items — including all color variants, size availability, pricing, technologies, and over a dozen attribute fields per product.
curl -X GET 'https://api.parse.bot/scraper/0bfa8a5a-9821-4b49-be06-c8f831b54aaa/get_products?limit=5&start=0&category=hombre-running' \ -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 adidas-cl-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.
"""Walkthrough: Adidas Chile SDK — browse catalog, drill into details."""
from parse_apis.adidas_chile_products_api import AdidasChile, Category, ProductNotFound
client = AdidasChile()
# List men's running shoes, capped at 5 items total.
for product in client.productsummaries.list(category=Category.HOMBRE_RUNNING, limit=5):
print(product.name, product.price, product.rating)
# Drill into one product's full details via .first()
summary = client.productsummaries.list(category=Category.MUJER_RUNNING, limit=1).first()
if summary:
detail = summary.details()
print(detail.name, detail.pricing_information.current_price)
for variation in detail.variation_list[:3]:
print(variation.size, variation.gtin)
# Batch-fetch products by ID with typed error handling.
try:
for product in client.products.get_many(product_ids="JH6206,JN3716", limit=3):
print(product.name, product.attribute_list.color, product.attribute_list.technologies)
except ProductNotFound as exc:
print(f"Product not found: {exc.product_ids}")
print("exercised: productsummaries.list / details / products.get_many")Retrieve product listings filtered by taxonomy category. Categories combine gender (hombre/mujer/ninos), sport (running/futbol/basketball/tenis/training), product type (zapatillas/ropa), and color segments with hyphens. Returns a paginated window into the catalog; advance with the start offset. Each product summary includes pricing, rating, available sizes, and technology tags. Total catalog depth for a given category is in total_count.
| Param | Type | Description |
|---|---|---|
| limit | integer | Maximum number of products to return from the current page. |
| start | integer | Pagination offset (0-based). Each page returns up to 48 items by default. |
| category | string | Taxonomy category filter. Combine segments with hyphens for multiple filters. Accepted segments include gender (hombre, mujer, ninos), sport (running, futbol, basketball, tenis, training), product type (zapatillas, ropa, zapatos_de_futbol), and colors (negro, blanco, rojo). |
{
"type": "object",
"fields": {
"category": "string - the category filter used",
"products": "array of product summary objects with product_id, name, price, sale_price, rating, technologies, available_sizes",
"view_size": "integer - items per page from API",
"start_index": "integer - current pagination offset",
"total_count": "integer - total products matching the filter",
"products_returned": "integer - actual products in this response"
}
}About the Adidas API
Browsing the Catalog
The get_products endpoint returns paginated product listings from adidas.cl. The category parameter accepts hyphen-combined taxonomy segments — for example, hombre-running for men's running products or mujer-zapatillas for women's shoes. Pagination is controlled with start (0-based offset) and limit. Each page contains up to 48 items, and the response includes total_count so you can calculate how many pages exist. Each product object in the products array exposes product_id, name, price, sale_price, rating, technologies, and available_sizes.
Product Detail Data
The get_product_details endpoint accepts a comma-separated list of product_ids sourced from get_products results. The response per product includes view_list (all product images with metadata), variation_list (per-size SKU codes and GTINs), product_link_list (color variants with images and prices), and pricing_information with currentPrice, standard_price, and standard_price_no_vat. The attribute_list object covers brand, color, gender, sport, technologies, weight, and surface — useful for building filters or structured product feeds.
Coverage and Filtering
Supported gender segments are hombre, mujer, and ninos. Sport filters include running, futbol, basketball, tenis, and training. Product type filters include zapatillas and ropa. These segments can be combined with hyphens in the category param, allowing targeted queries like ninos-futbol or mujer-training-ropa without any additional query syntax.
The Adidas API is a managed, monitored endpoint for adidas.cl — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when adidas.cl 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 adidas.cl 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?+
- Track sale prices and standard prices across adidas.cl to monitor discounts on specific categories
- Build a size-availability checker by querying
variation_listfromget_product_detailsfor target product IDs - Aggregate product technology tags (e.g. Boost, Primeknit) across the
hombre-runningcategory for feature comparison - Sync a product feed for an affiliate or comparison site using paginated
get_productsresults withtotal_countfor full coverage - Extract GTIN codes from
variation_listto match adidas.cl SKUs with other regional catalog data - Monitor color variant availability by polling
product_link_listfor specific products over time - Filter children's footwear by combining
ninosandzapatillassegments to scope a niche catalog segment
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Adidas have an official developer API for its product catalog?+
How do I retrieve all products in a category when there are more than 48 results?+
get_products response includes total_count and view_size. Increment the start parameter by view_size on each subsequent request until you have fetched all records. For example, if total_count is 144 and view_size is 48, you need three requests with start values of 0, 48, and 96.Does `get_product_details` return stock levels or inventory counts?+
variation_list with their SKU codes and GTINs, but does not expose numeric stock counts or real-time inventory levels. You can fork this API on Parse and revise it to add an inventory-focused endpoint if stock quantities are available from the source.Are customer reviews or ratings data returned beyond the aggregate rating field?+
get_products endpoint returns an aggregate rating field per product. Individual review text, reviewer details, and rating breakdowns are not covered by either endpoint. You can fork this API on Parse and revise it to add a reviews endpoint targeting that data.Can I filter products by price range or sort order through the API?+
get_products endpoint supports filtering via the category taxonomy parameter, limit, and start for pagination. Price range filtering and explicit sort order are not exposed as parameters. You can fork this API on Parse and revise it to add those input options.