Coppel APIcoppel.com ↗
Access Coppel.com product listings, prices, categories, and filters via API. Search by keyword, browse departments, and paginate across 1.3M+ products.
What is the Coppel API?
The Coppel.com API gives developers structured access to Mexico's largest department store catalog through 3 endpoints covering keyword search, category browsing, and full catalog pagination. The search_products endpoint returns product name, brand, SKU, pricing, sale status, and a category breakdown for any query. Each response includes discounted_price, image_url, and product_url fields alongside aggregate counts needed for pagination.
curl -X GET 'https://api.parse.bot/scraper/544e0bcc-735b-4947-ab82-fe7e6cdd3933/search_products?page=1&query=Tenis&order_by=1&page_size=5' \ -H 'X-API-Key: $PARSE_API_KEY'
Full-text search over Coppel.com product catalog by keyword. Returns paginated product listings with pricing, brand, badges, seller info, delivery options, and a category breakdown showing how results distribute across departments. Paginates via page number; each product exposes installment financing terms. Sorting controls relevance, price, or recency ordering.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number (1-based) |
| query | string | Search keyword (e.g., 'zapatos', 'laptops', 'iPhone') |
| order_by | string | Sort order for results |
| page_size | integer | Number of products per page (max ~48) |
{
"type": "object",
"fields": {
"page": "integer, current page number",
"query": "string, the search keyword used",
"products": "array of product objects with name, brand, sku, part_number, image_url, product_url, price, discounted_price, currency, is_on_sale, badges, seller, installment_amount, installment_duration, delivery",
"page_size": "integer, number of products per page",
"categories": "array of category objects with id, name, count, href",
"total_count": "integer, total number of matching products",
"total_pages": "integer, total number of pages available"
},
"sample": {
"data": {
"page": 1,
"query": "Tenis",
"products": [
{
"sku": "629218670",
"name": "Tenis para Correr Adidas Duramo Rc2 para Mujer",
"brand": "Adidas",
"price": 1499,
"badges": [],
"seller": "Adidas",
"currency": "MXN",
"delivery": {
"shipment": true,
"marketplace": true,
"store_pickup": false
},
"image_url": "https://cdn5.coppel.com/mkp/629218670-1.jpg",
"is_on_sale": false,
"part_number": "MKP-629218670",
"product_url": "https://www.coppel.com/pdp/tenis-para-correr-adidas-duramo-rc2-para-mujer-mkp-629218670",
"discounted_price": null,
"installment_amount": "91",
"installment_duration": "24"
}
],
"page_size": 5,
"categories": [
{
"id": "cat000774",
"href": "/ct/zapatos/cat000774",
"name": "Zapatos",
"count": "19632"
}
],
"total_count": 20479,
"total_pages": 4096
},
"status": "success"
}
}About the Coppel API
What the API Covers
The Coppel.com API exposes product data across Coppel's full inventory — electronics, appliances, clothing, furniture, and more — through three endpoints. Every product object carries name, brand, sku, part_number, image_url, product_url, price, discounted_price, currency, and is_on_sale. Pagination is consistent across all endpoints using page, page_size (up to ~48 per page), total_count, and total_pages.
Endpoint Breakdown
search_products accepts a query string (e.g., 'zapatos', 'iPhone') and an optional order_by sort parameter, returning matching products plus a categories array that shows how results distribute across departments — useful for understanding query intent. get_product_listings targets category or department browsing via a search_term param (e.g., 'Celulares', 'Muebles') and adds an available_filters object whose keys are filter categories (brands, colors, sizes, discounts, sellers, specs), each holding an array of options with id and count.
Full Catalog Browsing and Filtering
browse_catalog pages through Coppel's entire product catalog, which the endpoint documents at approximately 1.3 million products. It accepts optional client-side filters: seller (exact string match), shipment (boolean), marketplace (boolean — pass false to exclude third-party listings), and min_discount (computed from ((price - discounted_price) / price) * 100). When filters are applied, total_count reflects the window scanned rather than the full catalog. Each result in the results array includes a delivery object and a discount_percentage field not present in the other endpoints.
Coverage Notes
All three endpoints return product-level data only. Individual product detail pages, customer reviews, stock-level availability, and store-specific inventory are not part of the current response shape. The catalog skews toward Coppel's Mexican market; pricing and currency fields reflect MXN.
The Coppel API is a managed, monitored endpoint for coppel.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when coppel.com 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 coppel.com 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 price drops on specific SKUs by comparing
pricevsdiscounted_priceover time usingsearch_products. - Build a category-level price index for Mexican consumer electronics using
get_product_listingswithsearch_termset to department names. - Filter the full catalog to Coppel-direct listings only by passing
marketplace: falseandseller: 'Coppel'tobrowse_catalog. - Identify the deepest discounts in any category using the
min_discountfilter onbrowse_catalog. - Populate a product comparison tool with images and specs by pulling
image_url,brand, andpart_numberfrom search results. - Analyze category distribution of keyword search results using the
categoriesarray returned bysearch_products. - Enumerate available brand and size filters for a department by inspecting
available_filtersfromget_product_listings.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Coppel have an official public developer API?+
How does `browse_catalog` handle filtering versus the other two endpoints?+
browse_catalog applies filters client-side across a scanned window of the catalog rather than using pre-built facets. That means total_count when filters like min_discount or seller are active reflects the scanned subset, not the full 1.3M-product catalog. The search_products and get_product_listings endpoints return server-side total_count values that match the full query result.Does the API return individual product detail pages with full specifications?+
Are customer reviews or ratings included in the response?+
What is the maximum number of results per page, and how should I paginate?+
page_size at approximately 48 results per page. Use the total_pages field in any response to determine how many pages exist for a given query, then increment the page parameter (1-based) to iterate through results.