Mexican retail as JSON, with the credit plan reported as a plan and not as the price
Coppel API returns live Coppel data as clean JSON for coppel The primary endpoint, search, returns matching records including product id, default variant id, title, brand and image.
3 active endpoints, on 1 and 2 credit tiers.
- POST/coppel/v1/search
- POST/coppel/v1/category
- POST/coppel/v1/product/detail
What Coppel endpoints does ReefAPI ship?
3 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Coppel API
3 of 3 endpoints, ready to run
Search coppel.com by keyword, exactly as Coppel's own search box does. Every product comes back with the price you actually pay today in MXN, the struck original price and the discount when there is one, Coppel's published monthly instalment plan (amount, term and the higher credit total — Coppel is a credit retailer, so this is the number most of its customers act on), the brand, whether Coppel or a marketplace store sells it, the delivery options, the sale badges and the product URL. Page through the whole result set, sort by price, narrow by brand or by any facet Coppel publishes (offer step, colour, seller, screen size, RAM…), and read the facet list back so the next call can drill down. A keyword with no match answers an honest empty result, not an error.
{ "ok": true, "data": { "results": [ { "product_id": "PM-2298093", "sku": "229809", "default_variant_id": "IM-2298093-0", "title": "Pantalla Smart TV Hisense MiniLED-Hi-QLED 65 Pulgadas 4K 65QD8SV", "brand": "Hisense", "url": "https://www.coppel.com/pdp/pantalla-smart-tv-hisense-miniled-hi-qled-65-pulgadas-4k-65qd8sv-pm-2298093", "image": "https://cdn5.coppel.com/pm/2298093-1.jpg", "price": 9999, "list_price": 14699, "discount_pct": 32, "currency": "MXN", "on_sale": true, "installments": { "monthly_amount": 559, "months": 24, "credit_total": 13399, "currency": "MXN", "credit_markup_pct": 34 }, "badges": [ { "label": "Oferta", "group": "1", "variant": null } ], "delivery": { "home_delivery": true, "store_pickup": true, "marketplace_shipping": false }, "variant_types": { "has_size": false, "is_marketplace": false, "is_clothing": false, "is_furniture": true, "is_motorcycle": false, "is_phone": false } }, { "product_id": "PM-2276543", "sku": "227654", "default_variant_id": "IM-2276543-0", "title": "Pantalla Smart TV TCL QLED 43 Pulgadas FHD 43Q3K", "brand": "TCL", "url": "https://www.coppel.com/pdp/pantalla-smart-tv-tcl-qled-43-pulgadas-fhd-43q3k-pm-2276543", "image": "https://cdn5.coppel.com/pm/2276543-1.jpg", "price": 5299, "list_price": null, "discount_pct": null, "currency": "MXN", "on_sale": false, "installments": { "monthly_amount": 297, "months": 24, "credit_total": 7101, "currency": "MXN", "credit_markup_pct": 34 }, "badges": [ { "label": "Solo en línea", "group": "2", "variant": null } ], "delivery": { "home_delivery": true, "store_pickup": true, "marketplace_shipping": false }, "variant_types": { "has_size": false, "is_marketplace": false, "is_clothing": false, "is_furniture": true, "is_motorcycle": false, "is_phone": false } }, { "product_id": "MKP-74891538", "sku": "74891538", "default_variant_id": "IMKP-74891538N4805", "title": "Pantalla TV AOC Roku TV Led 32 HD Smart TV 32S5045 para Streaming", "brand": "AOC", "url": "https://www.coppel.com/pdp/pantalla-tv-aoc-roku-tv-led-32-hd-smart-tv-32s5045-para-streaming-mkp-74891538", "image": "https://cdn5.coppel.com/mkp/74891538-1.jpg", "price": 2199, "list_price": 3349, "discount_pct": 34, "currency": "MXN", "on_sale": true, "installments": { "monthly_amount": 133, "months": 24, "credit_total": 3189, "currency": "MXN", "credit_markup_pct": 45 }, "badges": [ { "label": "Oferta", "group": "1", "variant": null } ], "delivery": { "home_delivery": true, "store_pickup": false, "marketplace_shipping": true }, "variant_types": { "has_size": false, "is_marketplace": true, "is_clothing": false, "is_furniture": false, "is_motorcycle": false, "is_phone": false } } ], "count": 3, "total_results": 624, "page": 1, "page_size": 48, "currency": "MXN" }, "meta": { "api": "coppel", "endpoint": "search" } }
How the Coppel API works
Coppel is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 321 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and cache hits cost nothing.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
Read the cash price and the credit total as two different numbers, because Coppel sells on credit
Coppel is a credit retailer before it is a shop. The number on the shelf and the number a customer actually pays over twenty-four months are not the same, and a price comparison that mixes them is wrong in one direction only.
{"query": "licuadora"}2 credits for twenty-four rows. Each row carries price as what you pay today, list_price as the struck original where there is one, and installments with the monthly amount, the number of months, the credit total and the mark-up that total represents.
{"query": "licuadora", "filters": "attr_facet_marca=Oster"}2 credits. Coppel's own facet values come back on the unfiltered call as paste-ready strings, because its filter input needs both halves of the pair and half of one is a validation error rather than an empty list.
{"category": "<id or category URL>"}2 credits. The same rows and facets for a whole department, plus the breadcrumb, the category's own page title and meta description, and the sub-categories underneath it with their counts.
{"product_id": "<part number, bare number, or the product URL>"}1 credit. The long description with its HTML stripped, every published specification, every image, the seller, home delivery and store pickup, and each variant with its own price and its own instalment plan.
A price you can compare like for like, a credit total you can quote separately, and a variant table where each size or colour carries its own figure.
curl -X POST https://api.reefapi.com/coppel/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"televisor"}'{
"ok": true,
"data": { … },
"meta": {
"api": "coppel",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}Mexico only, in pesos, with the instalment plan reported as its own number
Measured 2026-09-30 against the live gateway across seven keyword searches, one category and several product records, ninety-six rows read field by field. Three of these lines go against us.
Coppel runs one national storefront and every figure comes back in MXN. There is no country parameter because there is no second country to point it at, and no currency parameter because the source publishes one currency. Both the Coppel catalogue and its third-party marketplace are in the same result set, and the seller field says which one a row came from.
Every row measured carried an instalment plan, and on every one of them the credit total was higher than the cash price. One blender listed at 1,499 pesos in cash is 24 payments of 87, which is 2,084 and a mark-up of thirty-nine percent. Both numbers are Coppel's own: price is what you pay today, installments.credit_total is what the published plan adds up to, and credit_markup_pct is the difference between them. The plan is never returned as the price.
Where a product is discounted, Coppel's own payload carries both figures, and the higher one is the struck original rather than the amount charged. Publishing that as the price would overstate an item by whatever the discount is - on one marketplace row, 43,999 against an actual 35,799. list_price and discount_pct carry the markdown; price is always what you pay.
Eighty-nine of ninety-six rows carried a struck original and a discount percentage. The other seven are simply not on sale, so the source publishes no original price and the engine returns null rather than copying the current price into both slots, which would report every product as zero percent off.
Ascending and descending price sorts were checked for monotonicity on the returned figures rather than taken on trust: ascending ran 289, 359, 375, 375 upward and descending ran 74,544 down to 47,599 without an inversion. Only the sort codes whose effect could be verified are published; three more exist in the site's own bundle without labels and are not offered.
Filtering twenty-four rows to a single brand returned twenty-four rows of that brand and zero of any other. Coppel's filter input requires a key and a value together, so the engine hands back each facet value as a complete paste-ready string instead of leaving a caller to assemble one that validates as an error.
Coppel loosens a query it cannot match rather than answering empty, so a nonsense phrase containing a number can come back with two dozen unrelated items. The response says which happened: query_type reads lexic-rules on a genuine match and lexic-minimum when the source relaxed the query, and a keyword with nothing at all behind it returns zero rows honestly. Read query_type before trusting a surprising result set.
Every datacentre exit is refused outright at the edge - not a challenge, a flat refusal - on the storefront, on the internal data endpoints and on robots.txt alike. A Mexican residential vantage point gets everything on the first request with no cookie at all. That cost is ours, but it is why a search here carries a heavier price than a cheap open source.
Coppel's listing surface carries no rating, no review count, no stock number and no seller rating, so none of those come back. What is there is complete: product id, title, price, currency, image, brand, sku, seller, badges, delivery, variant types and the instalment plan were present on ninety-six of ninety-six rows.
Two credits for a search or a category page of twenty-four rows, one credit for a product record. A search call costs roughly 36 to 74 KB of residential traffic, which is what the two-credit search reflects.
What people build with Coppel
The jobs this data is most often used for.
endpoints
credits per call
Pricing and assortment teams use Coppel to search coppel.com by keyword, exactly as Coppel's own search box does.
Brand-protection teams use Coppel to get every product in a Coppel category, by category id or category URL, paged.
Retail analysts use Coppel to get the full Coppel product record by part number, bare product number or product URL.
What Coppel data costs
The cheapest call here is 1 credit, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
Full pricing →- 1,000 free credits on signup, no card
- One key, all 321 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/coppel/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"televisor"}'import requests
r = requests.post(
"https://api.reefapi.com/coppel/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"query": "televisor"
},
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Coppel.
Get a free key →What is the Coppel API?▾
Coppel API is a ReefAPI endpoint group for coppel It returns live JSON through POST requests under /coppel/v1.
Is the Coppel API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Coppel calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Coppel login or account?▾
No login to Coppel is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Coppel data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Coppel API use?▾
Coppel actions currently cost 1-2 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call Coppel from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call coppel actions with the same key, credit pool and JSON envelope used by normal REST requests.
Is the Coppel API a Coppel scraper?▾
It is the managed alternative to a DIY Coppel scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same coppel back as clean JSON.
Why does my Coppel scraper keep getting blocked?▾
Most Coppel scrapers break on anti-bot defenses, rate limits and IP bans that need rotating residential proxies and browser fingerprinting to clear. ReefAPI handles all of that for you — no proxies, no captchas, no maintenance — and returns live JSON. Blocked calls are free.
26 More APIs APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Coppel, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 320 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-09-30.