Reef AI: ask for any data. Try it
Looking for the overview — what this API returns, what it costs, and a call you can run without a key? See the Card Rush API page →
E-commerce & Marketplaces

Card Rush API & Scraper

The Card Rush API turns the Card Rush shops (カードラッシュ, cardrush-pokemon.jp and its nine sister shops) into JSON in three actions.

3 actionsLive JSON1,000 free credits$0.67–$1.50 / 1,000 creditsMCP-ready
Get a free keyOpen in playground

🤖 Using an AI assistant? Copy this link into ChatGPT / Claude / Cursor — it reads every endpoint and parameter instantly and tells you if this API fits your use case.

search finds products by name, card number or set on one game's shop, or lists a set / feature page (group) or a category, with an in-stock filter and price or recommended order, 10 to 100 rows a page. Every row is one product, which at Card Rush means one card in one condition or one graded slab: the price in yen including tax, the web-shop stock, and the parts of the shop's title split into fields: condition (状態 S, A-, B, C, and 難 for a damaged copy; NM / EX+ / EX / HPLD / POOR on Magic), the grader, grade and grade_label of a slab (PSA, BGS, CGC, ARS, PCG and the other graders the shop writes), rarity, card number, the set code on Pokémon, and the language on Magic. card returns one product with the most one order can take, its category, the large image and every photo of the product gallery in page order (on many products the photos after the first show the actual copy). buying_prices returns the shop's buying-price list (買取表): what Card Rush pays for a card in yen, with the card number, rarity, set, the date it was updated and the id of the shop product it refers to. Ten games: Pokémon, One Piece, Yu-Gi-Oh!, Magic: The Gathering, Duel Masters, Battle Spirits, Digimon, Vanguard, Dragon Ball Fusion World and Shadowverse: Evolve (no buying list for Shadowverse). One ReefAPI key, the standard { ok, data, meta, error } envelope, no Card Rush account.

Reference

How Card Rush writes condition and grade — and the fields they become

Card Rush lists every condition of a card as its own product and writes the condition into the product title. The API splits it out; the full title stays in name.

in the shop titlefieldvalue
〔状態A-〕ピカチュウ【C】{033/087}conditionA-
〔状態B〕 / 〔状態C〕conditionB / C
〔PSA10鑑定済〕ミュウ【-】{016/036}graded, grader, gradetrue, PSA, 10
〔※状態難/CGC10黒鑑定済〕condition, grader, grade, grade_label難, CGC, 10, black (a black-label slab whose card or case is damaged)
【SAR】 / 【SEC】 / 【ウルトラ】raritySAR / SEC / ウルトラ
{025/165} / {OP13-118}card_number025/165 / OP13-118
[EX+]稲妻/Lightning Bolt《日本語》【A25】 (Magic)condition, language, set_codeEX+, 日本語, A25
☆SALE☆on_saletrue (one per customer: max_order_qty 1)

When the shop writes no condition bracket, condition is null rather than guessed. Prices are yen including consumption tax (税込), written by the shop with a thousands comma (32,800円 = 32800).

Live example

Real request and response JSON

Captured from the indexed primary action, search, on .

Captured request
{
  "method": "POST",
  "url": "https://api.reefapi.com/cardrush/v1/search",
  "headers": {
    "x-api-key": "$REEF_KEY",
    "content-type": "application/json"
  },
  "body": {
    "query": "ピカチュウ",
    "per_page": 20
  }
}
Captured response
{
  "ok": true,
  "meta": {
    "api": "cardrush",
    "endpoint": "search",
    "mode": "live",
    "latency_ms": 1529.6,
    "record_count": 20,
    "bytes": 158903,
    "cache_hit": false,
    "game": "pokemon",
    "shop": "www.cardrush-pokemon.jp",
    "listing": "keyword",
    "total": 3708,
    "page": 1,
    "per_page": 20,
    "last_page": 186,
    "has_more": true,
    "past_last_page": false,
    "sort": "relevance",
    "filters_applied": {
      "query": "ピカチュウ"
    },
    "facets": {
      "categories": [
        {
          "id": "20",
          "name": "キズ有特価",
          "count": 1537
        },
        {
          "id": "23",
          "name": "未開封BOX",
          "count": 48
        },
        {
          "id": "25",
          "name": "オリパ",
          "count": 2
        }
      ],
      "groups": [
        {
          "id": "594",
          "name": "拡張パック「30th CELEBRATION」",
          "count": 130
        },
        {
          "id": "522",
          "name": "スタートデッキ100 バトルコレクション",
          "count": 23
        },
        {
          "id": "523",
          "name": "スタートデッキ100 バトルコレクション コロちゃおVer.",
          "count": 4
        }
      ]
    },
    "currency": "JPY",
    "upstream_requests": 1,
    "warnings": [],
    "charged_credits": 3,
    "version": "1.0.0",
    "request_id": "e3643db0b5d7447a",
    "queue_ms": 1.3,
    "fetched_at": "2026-10-15T17:02:51.939Z"
  },
  "data": {
    "rows": [
      {
        "id": "1123",
        "product_id": "1123",
        "game": "pokemon",
        "url": "https://www.cardrush-pokemon.jp/product/1123",
        "name": "ピカチュウ【-】{004/004}",
        "condition": null,
        "graded": false,
        "grader": null,
        "grade": null,
        "on_sale": false,
        "sealed": false,
        "rarity": null,
        "card_number": "004/004",
        "attribute": null,
        "language": null,
        "set_code": null,
        "card_name": "ピカチュウ",
        "model_number": "その他",
        "price_jpy": 18800,
        "price_includes_tax": true,
        "in_stock": true,
        "stock_qty": 11,
        "stock_unit": "枚",
        "image": "https://www.cardrush-pokemon.jp/data/cardrushpokemon/_/70726f647563742f70696b61747975753031342e6a7067003136300000660023666666666666.jpg"
      },
      {
        "id": "1130",
        "product_id": "1130",
        "game": "pokemon",
        "url": "https://www.cardrush-pokemon.jp/product/1130",
        "name": "ピカチュウ【C】{033/087}",
        "condition": null,
        "graded": false,
        "grader": null,
        "grade": null,
        "on_sale": false,
        "sealed": false,
        "rarity": "C",
        "card_number": "033/087",
        "attribute": null,
        "language": null,
        "set_code": "CP6",
        "card_name": "ピカチュウ",
        "model_number": "CP6",
        "price_jpy": 32800,
        "price_includes_tax": true,
        "in_stock": true,
        "stock_qty": 52,
        "stock_unit": "枚",
        "image": "https://www.cardrush-pokemon.jp/data/cardrushpokemon/_/70726f647563742f70696b61747975753033332e6a7067003136300000660023666666666666.jpg"
      },
      {
        "id": "1121",
        "product_id": "1121",
        "game": "pokemon",
        "url": "https://www.cardrush-pokemon.jp/product/1121",
        "name": "ピカチュウ【-】{001/010}",
        "condition": null,
        "graded": false,
        "grader": null,
        "grade": null,
        "on_sale": false,
        "sealed": false,
        "rarity": null,
        "card_number": "001/010",
        "attribute": null,
        "language": null,
        "set_code": null,
        "card_name": "ピカチュウ",
        "model_number": "その他",
        "price_jpy": 14800,
        "price_includes_tax": true,
        "in_stock": true,
        "stock_qty": 12,
        "stock_unit": "枚",
        "image": "https://www.cardrush-pokemon.jp/data/cardrushpokemon/_/70726f647563742f70696b61747975756b61776169692e6a7067003136300000660023666666666666.jpg"
      }
    ]
  }
}
Actions

What the Card Rush API does

ActionDescriptionConcrete use caseKey params
searchSearch one Card Rush shop. Each row is one product (one card in one condition / grade) with its price, stock and the parts of its title (condition, grader and grade, rarity, card number). Give `query`, or `group` (a set / feature listing), or `category`. With a query, group and category narrow it.Pricing teams call search to search one Card Rush shop.game, query, group, category, in_stock_only, ...
cardOne Card Rush product in full: price, stock, the most one order can take, category, the shop's note, the large image and every photo of the product gallery.Marketplace operators call card to get one Card Rush product in full.product_id, game
buying_pricesCard Rush's buying-price list (買取表): what the shop pays for a card, in JPY. This is a BUY price — never the sale price. Each row links to the shop product it refers to.Catalog enrichment teams call buying_prices to get card Rush's buying-price list (買取表).game, query, card_number, rarity, pack_code, ...
Code samples

Call search from your stack

curl -X POST https://api.reefapi.com/cardrush/v1/search \
  -H "x-api-key: $REEF_KEY" \
  -H "content-type: application/json" \
  -d '{"query":"ピカチュウ","per_page":20}'
MCP one-liner
Ask your MCP-connected assistant: call reefapi.cardrush.search with {"query":"ピカチュウ","per_page":20}.
Use cases

Who uses this API and why

  • Price a Japanese card collection: search each card and read the sale price per condition and PSA grade.
  • Spread between buy and sell: buying_prices for a set's chase cards, then card on each shop_product_id for Card Rush's own sale price.
  • Watch a new set: search with the set's group id and sort=price_desc every day.
  • Find graded slabs: search PSA10 on any of the ten shops.
  • Cross-market comparison: Card Rush yen prices next to Cardmarket euro and TCGplayer dollar prices for the same card number.
FAQ

Questions developers ask before integrating

Which games does it cover?

Pokémon (default), One Piece, Yu-Gi-Oh!, Magic: The Gathering, Duel Masters, Battle Spirits Saga, Digimon, Cardfight!! Vanguard, Dragon Ball Super Fusion World and Shadowverse: Evolve, each Card Rush shop of its own, chosen with game. All ten answered search on 2026-10-15. The buying-price list exists for nine of them; Card Rush publishes none for Shadowverse: Evolve.

Is the buying price the price I pay?

No. buying_prices returns buy_price_jpy, what Card Rush pays when you sell a card to the shop (買取価格). It is never returned as price. The sale price is price_jpy on search and card. Each buying-price row carries shop_product_id, so card gives you the shop's sale price and stock for the same card.

How do conditions and graded cards work?

Card Rush sells each condition as a separate product with its own price and stock, so a search for one card returns the copy without a condition bracket and, for example, 〔状態A-〕, 〔状態B〕 and 〔状態C〕 copies as separate rows. condition carries the grade the shop wrote; graded, grader and grade are filled for slabs from PSA, BGS, CGC, ARS, PCG and the other graders the shop uses, and grade_label is black for a CGC or BGS black label. A combined bracket such as 〔※状態難/PSA10鑑定済〕 is a slab with a damaged card or case: it comes back as condition 難 next to grader PSA and grade 10. Search PSA10 to list slabs.

How do I list one set?

Every search answer carries meta.facets.groups and meta.facets.categories: the shop's own set / feature listings and categories with their ids and counts for that result. Pass a group id (for example 594, 拡張パック「30th CELEBRATION」 on the Pokémon shop) to list the set, or combine it with query to narrow a name search. Without a query, give one group or one category per call.

How far can I page?

10, 20, 30, 50 or 100 rows a page (100 by default); meta.total is the shop's own count (3,708 products for ピカチュウ on the Pokémon shop) and meta.last_page is computed from it. A page past the end returns no rows with past_last_page true. With a keyword, the default relevance order can swap tied rows between requests; sort by price_asc, price_desc or featured to page through a large result.

Is the stock number real?

stock_qty is the web shop's stock as the product page prints it (在庫数). Card Rush notes that its physical stores keep separate stock. A sold-out product keeps its price and comes back with in_stock false and stock_qty 0.

How current is the buying list?

Every call reads the live list. meta.list_updated is the list's own 'as of' label in Japan time, and every row has updated_at. Rows flagged is_hot are the ones the shop marks 只今の買取額UP; hot_only=true lists only those.

What is the Card Rush API?

Card Rush API is a ReefAPI endpoint group for card rush (カードラッシュ) trading-card prices as json: what one of japan's largest card shops sells a pokémon, one piece, yu-gi-oh! or mtg card for, in which condition and how many it has, and what it pays for one (買取). It returns live JSON through POST requests under /cardrush/v1.

Is the Card Rush API free to try?

Yes. ReefAPI starts with 1,000 free credits, no card required. Card Rush calls use the same shared credit balance as every other ReefAPI engine.

Do I need a Card Rush login or account?

No login to Card Rush 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 Card Rush 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 Card Rush API use?

Card Rush actions currently cost 2-3 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.

Can I call Card Rush from an AI assistant or MCP client?

Yes. Connect ReefAPI once through MCP and your assistant can call cardrush actions with the same key, credit pool and JSON envelope used by normal REST requests.

Is the Card Rush API a Card Rush scraper?

It is the managed alternative to a DIY Card Rush 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 card rush (カードラッシュ) trading-card prices as json: what one of japan's largest card shops sells a pokémon, one piece, yu-gi-oh! or mtg card for, in which condition and how many it has, and what it pays for one (買取) back as clean JSON.

Questions developers ask about Card Rush data

From Stack Overflow, Reddit and search, answered with live calls on 2 Nov 2026.

Is there a Card Rush API for card prices, or do I have to scrape the shop?▾

Card Rush runs a separate web shop for each game (cardrush-pokemon.jp, cardrush-op.jp, cardrush.jp for Yu-Gi-Oh!, cardrush-mtg.jp and more), and the Card Rush price trackers developers publish on GitHub all parse those shop pages themselves; none of them calls a Card Rush API.

ReefAPI's Card Rush API gives you the same shop data as JSON: paste a product URL or id into card and you get the yen price with tax, the condition, the web-shop stock and the category. Desktop and /phone/ links both work.

curl · card from a product URL
curl -X POST https://api.reefapi.com/cardrush/v1/card \
  -H "x-api-key: $REEF_KEY" -H "content-type: application/json" \
  -d '{"game":"onepiece","product_id":"https://www.cardrush-op.jp/phone/product/9527"}'

Real response, 2 Nov 2026: "シェパード・十・ピーター聖 (パラレル/赤文字/illust:Gege Akutami)【R/P】{OP13-084}" · price_jpy 19800 · in_stock false · category 黒

Why is the Card Rush price so different from TCGplayer for the same card?▾

Collectors on r/PokeInvesting compared Carmine SAR (ゼイユ, 130/101) at 23,800 yen on Card Rush with $95-100 on TCGplayer, and the replies pointed out that US prices tend to follow Japanese price moves with a delay, most of all on cards that sell rarely.

Before comparing, make sure you read the right Card Rush row: the shop lists the clean copy, each lower condition and each graded slab as separate products. Search the Japanese name with the card number and take the row where condition and grader are empty.

curl · one card, every copy
curl -X POST https://api.reefapi.com/cardrush/v1/search \
  -H "x-api-key: $REEF_KEY" -H "content-type: application/json" \
  -d '{"query":"ゼイユ 130/101","per_page":20}'

Real response, 2 Nov 2026: 11 products · "ゼイユ【SAR】{130/101}" 17800 JPY, 17 in stock · 状態A- 12800 · 状態B 8980 · PSA 9 13800 · PSA 10 75800 (sold out)

How do I see what Card Rush pays for a card (its buylist, 買取 price)?▾

Card Rush publishes a separate buying-price list (買取表) for each game on cardrush.media, apart from the shop's selling prices, and one open-source Japanese TCG monitor on GitHub notes that the buylist page carries a caching notice, so check how fresh it is.

buying_prices returns that list filtered by card number, name, rarity or pack code, with the list's own update time in meta.list_updated. Each row's shop_product_id opens the matching shop product in card, which gives you the buy and sell price of the same card.

curl · buying price by card number
curl -X POST https://api.reefapi.com/cardrush/v1/buying_prices \
  -H "x-api-key: $REEF_KEY" -H "content-type: application/json" \
  -d '{"card_number":"217/187"}'

Real response, 2 Nov 2026: "ブラッキーex" SAR 217/187, テラスタルフェスex (SV8a) · buy_price_jpy 40000 · list_updated "11/03 06:45" JST · shop_product_id 62018 → sells for 54800 JPY, 48 in stock

How do I compare raw, condition A-/B and PSA 10 prices for one Japanese card on Card Rush?▾

Card Rush writes the condition or slab in front of the card name, such as 〔状態A-〕 or 〔PSA10鑑定済〕, and publishes the condition standards behind those letters, so collectors who buy there to grade see every copy priced on its own.

ReefAPI's Card Rush API splits that title into condition, grader, grade, grade_label (black for a CGC or BGS black label), rarity and card_number, including combined brackets such as 〔※状態難/PSA10鑑定済〕, a damaged slab with condition 難, so the raw-to-PSA 10 spread for a card is one search away.

curl · condition and grade spread
curl -X POST https://api.reefapi.com/cardrush/v1/search \
  -H "x-api-key: $REEF_KEY" -H "content-type: application/json" \
  -d '{"query":"ブラッキーex 217/187","per_page":20}'

Real response, 2 Nov 2026: raw 54800 JPY (48 in stock) · 状態A- 39800 · 状態B 19800 · 状態C 11800 · PSA 8 28800 · PSA 9 52800 · PSA 10 74800

How do I pull a whole Japanese set from Card Rush without duplicate pages?▾

One open-source Card Rush tracker on GitHub documents two problems when crawling by set: some queries keep returning rows after the last page instead of an empty page, and a bare set code such as M2 also matches M2a listings, so its authors search by set code plus rarity and deduplicate by product URL.

With ReefAPI, search the set code and rarity with sort: price_desc and per_page: 100, and stop when meta.has_more is false. A page past the end comes back empty with meta.past_last_page: true, and each row carries its set_code for filtering.

curl · one set, one rarity
curl -X POST https://api.reefapi.com/cardrush/v1/search \
  -H "x-api-key: $REEF_KEY" -H "content-type: application/json" \
  -d '{"query":"M2a SAR","sort":"price_desc","per_page":100}'

Real response, 2 Nov 2026: total 65, every row set_code M2a · "メガゲンガーex【SAR】{240/193}" 41800 JPY, 185 in stock · "ピカチュウex【SAR】{234/193}" 27800 · page 2 → 0 rows, past_last_page true

Can I track One Piece card prices from cardrush-op.jp, buy and sell side by side?▾

One Piece players on r/OnePieceTCG ask about cardrush-op.jp, the One Piece shop of Card Rush, which carries the same card in many parallel versions at very different prices.

Pass game: onepiece to both actions and join the buying list to the shop listing on shop_product_id. The same works for Yu-Gi-Oh!, MTG, Duel Masters, Digimon, Vanguard, Battle Spirits and Dragon Ball.

python · sell vs buy for one card number
import requests

def reef(action, body):
    r = requests.post(f"https://api.reefapi.com/cardrush/v1/{action}",
                      headers={"x-api-key": REEF_KEY}, json=body)
    return r.json()["data"]["rows"]

sell = {s["product_id"]: s for s in reef("search", {"game": "onepiece", "query": "OP13-118", "per_page": 100})}
for b in reef("buying_prices", {"game": "onepiece", "card_number": "OP13-118"}):
    s = sell.get(b["shop_product_id"])
    if s:
        print(s["name"], s["price_jpy"], b["buy_price_jpy"])

Real response, 2 Nov 2026: Luffy OP13-118 パラレル/漫画背景/漫画絵 SEC/SP: sells 298000, buys 220000 · パラレル/手配書 SP: sells 24800 (29 in stock), buys 15000 · 8 of 8 buy rows matched

docs / cardrush

Card Rush

Card Rush (カードラッシュ) trading-card prices as JSON: what one of Japan's largest card shops sells a Pokémon, One Piece, Yu-Gi-Oh! or MTG card for, in which condition and how many it has, and what it pays for one (買取).

base /cardrush/v13 endpoints
post/cardrush/v1/card2 credits

One Card Rush product in full: price, stock, the most one order can take, category, the shop's note, the large image and every photo of the product gallery.

ParameterAllowed / rangeDescription
product_idrequired—A search row's `product_id` (or a buying-price row's `shop_product_id`), or a Card Rush product URL such as https://www.cardrush-pokemon.jp/product/1130.
game = pokemonoptionalpokemon · onepiece · yugioh · mtg · duel_masters · battle_spirits · digimon · vanguard · dragon_ball · shadowverse_evolveWhich Card Rush shop: pokemon (cardrush-pokemon.jp, default), onepiece, yugioh (cardrush.jp), mtg, duel_masters, battle_spirits, digimon, vanguard, dragon_ball, shadowverse_evolve. Same fields on every shop.
Try in playground →
post/cardrush/v1/buying_prices2 credits

Card Rush's buying-price list (買取表): what the shop pays for a card, in JPY. This is a BUY price — never the sale price. Each row links to the shop product it refers to.

ParameterAllowed / rangeDescription
game = pokemonoptionalpokemon · onepiece · yugioh · mtg · duel_masters · battle_spirits · digimon · vanguard · dragon_ballWhich game's buying-price list: pokemon (default), onepiece, yugioh, mtg, duel_masters, battle_spirits, digimon, vanguard, dragon_ball. Shadowverse: Evolve has no published list.
queryoptional—Card or product name, partial match (Japanese).
card_numberoptional—The card number printed on the card (型番), e.g. 025/165, OP13-118, QCCP-JP004.
rarityoptional—Rarity as the list writes it (SAR, SR, AR, UR, SEC, シークレット, …).
pack_codeoptional—Set / pack code (パック記号), e.g. M2a, SV-P. Pokémon and Dragon Ball lists.
categoryoptional—One of the list's own sections for that game. pokemon: 最新弾, スタンダード, エクストラ, 旧裏, サプライ, パック · onepiece: 最新弾, 通常弾, サプライ, パック · yugioh: 最新弾, 通常弾, アジアシク, コレクター向け(初期系), ラッシュデュエル, サプライ, パック · mtg: 高額系, foil系, スタンダード, スタンダード最新弾, パイオニア以下, モダン以下最新弾 · duel_masters: 最新弾, 通常弾, 初期系, 高額系, サプライ, 未開封BOX · battle_spirits / digimon: 最新弾, 通常弾, サプライ · vanguard: 最新弾, Dスタン, Vスタン・Pスタン, サプライ · dragon_ball: 最新弾, 通常弾, 未開封BOX, サプライ. Default = the page's default (the single-card sections).
hot_only = falseoptional—Only cards the shop flags as 只今の買取額UP (buying price raised now).
sort = price_descoptionalprice_desc · price_ascOrder by buying price.
per_page = 100optional1–100Rows per page, 1-100 (default 100).
page = 1optional1–5000Page number; meta.last_page says how many there are.
Try in playground →
Built for volume
5M+ requests a day

Measured at 60 requests a second across the fleet, with no central bottleneck. Volume pricing is on request, and per-key limits are raised for high-volume accounts.

Missing a source?
We build it

Tell us a site we do not cover yet and it becomes an engine. A customer asked for bestprice.gr on a Sunday and it was in the catalog the next day.

Support
2 minute median reply

Median time from a question in the live chat to the first answer, measured across every answered conversation. Setup help included, no support tier to buy.

One key, one balance
Every API included

No per-site plans and no separate subscriptions. One key and one credit pool across the whole catalog, so adding a source costs nothing up front.

Planning something large? Tell us the volume and the sources and we will come back with what it costs and what we would have to build.