Trading-card catalogue research
Use Cardmarket endpoints to turn trading-card catalogue research into repeatable API requests with documented inputs and JSON responses.
Resolve the right game, set, language, and card version before comparing Cardmarket's public catalogue and daily guide snapshots; they are not live seller offers.
Search Cardmarket product catalogues and daily price-guide exports by game, category, expansion, and product ID.
Endpoint families
3
Documented params
22
Examples
5
Live catalog snapshot
Active endpoints
5
Methods
GET
Required params
5
Schema refs
5
{
"platform": "Cardmarket",
"endpoint": "cardmarket-games",
"method": "GET",
"path": "/cardmarket/games",
"auth": "apiKey"
}Use cases
Search Cardmarket product catalogues and daily price-guide exports by game, category, expansion, and product ID.
Use Cardmarket endpoints to turn trading-card catalogue research into repeatable API requests with documented inputs and JSON responses.
Use Cardmarket endpoints to turn daily price-guide snapshots into repeatable API requests with documented inputs and JSON responses.
Use Cardmarket endpoints to turn game, category, and expansion mapping into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Cardmarket endpoint catalog — 5 endpoints, 22 documented request parameters, and 5 published response schemas — the same catalog Docs and Playground run against.
5 documented Cardmarket endpoints, grouped into 3 request families — Catalog, Price Guide and Games.
22 request parameters are documented across those Cardmarket endpoints, 5 of them required — the full input contract is public before you write any integration code.
5 of the 5 Cardmarket endpoints ship a recorded example response, and 5 carry a documented response schema — you can code against the real JSON before the first request.
Cardmarket 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.
5 hosted MCP tools back the Cardmarket endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/cardmarket/catalog/categories
/cardmarket/price-guide/categories
/cardmarket/games
Endpoint catalog
/cardmarket/gamesReturns the exact observed public S3 price-guide IDs and whether singles/non-singles catalogue files are present. Product display names are not inferred from numeric IDs when the download index cannot provide a confirmed mapping.
MCP tool cardmarket_games
/cardmarket/catalog/categoriesReturns only the category and expansion values from the selected public product catalogue. Use this lightweight discovery route before filtering catalogues by category_id or expansion_id; it does not return product rows.
MCP tool cardmarket_catalog_categories
/cardmarket/catalogReads the public singles, non-singles, or global accessories export and applies local name/category/expansion filters. Category and expansion IDs and labels are discovered from the complete selected file. Game IDs 26-33 have price guides but no verified catalogue files. The response is a catalogue snapshot, not current seller offers.
MCP tool cardmarket_catalog
/cardmarket/price-guide/categoriesReturns only the numeric category IDs and counts in a game or global accessories price guide. Use this discovery route before filtering price guides by category_id; it does not return price rows.
MCP tool cardmarket_price_guide_categories
/cardmarket/price-guideReturns a paginated snapshot of Cardmarket's public daily price-guide export. The response discovers category IDs but the source file has no category labels. Cardmarket's posted English terms include a prior-written-agreement clause for external price display in a future-dated revision whose effective status is unconfirmed here; the response marks permission as unconfirmed.
MCP tool cardmarket_price_guide
Related APIs
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.
How to scrape Cardmarket
Cardmarket describes itself as a marketplace for game trading cards, and its seller guide stresses exact editions, languages, foil states, and condition because those attributes distinguish otherwise similar products. Crawlora's five production-published routes expose the game directory, product catalogue exports, and a separate daily price-guide export. On 2026-10-29, the game directory returned 31 IDs and the guide for `game_id=6` reported 80,170 rows. These are dated snapshots, not live seller offers or a transaction-history archive. A filtered catalogue read for that game exceeded a 35-second direct-probe budget while the ordinary catalogue monitor was UP, so plan for a cold export to take longer and preserve `fetched_at` and `stale` with each result. Cardmarket's terms require prior written agreement for external display of trading-card and price data; API access alone is not a redistribution license.
Start with `/cardmarket/games` and retain the returned numeric game ID with its label. The production response contained 31 game IDs on 2026-10-29. Singles and non-singles catalogue calls require `game_id`; the global accessories catalogue omits it.
Use `/cardmarket/catalog/categories` to obtain category and expansion IDs for the chosen game, then pass those returned values to `/cardmarket/catalog`. Its optional `q` is a case-insensitive product-name substring, not a seller or offer search. `limit` is 1–500 and `offset` is zero-based.
`/cardmarket/price-guide/categories` supplies IDs for the guide export; do not assume they match the catalogue's categories. `/cardmarket/price-guide` accepts an optional exact `product_id` filter and the same bounded `limit`/`offset` page controls. Game and global-accessories guides use different `kind` values.
The guide is a daily public export with average, low, trend, and period metrics where supplied; it is not a current seller-offer book or complete sale history. Retain the returned `fetched_at`, `stale`, and price-redistribution status fields, and do not interpret missing period values as zero.
Cardmarket's own seller guide treats edition, language, foil, signed/altered state, and condition as separate listing facts. Join on returned product IDs and keep those attributes with any comparison; a broad name match can combine different printings or languages.
FAQ
No. It searches a product-catalogue snapshot. The price guide is a separate daily export, and neither route represents the current offer book or every historical transaction.
No. Discover catalogue categories through `/cardmarket/catalog/categories` and price-guide categories through `/cardmarket/price-guide/categories`; keep each ID with its route and game.
The service downloads a full game file and applies category, expansion, name, and page filters locally. Files are cached for 12 hours, and a stale snapshot may be served after an upstream refresh failure. Keep `fetched_at` and `stale` rather than treating a timeout or stale file as current inventory.
No. Cardmarket's current terms say external display of cards and prices requires prior written agreement. The price-guide response includes a redistribution-status field; it is not itself permission to republish the data.