What Card Rush sells a card for in Japan, and what it pays for one
The Card Rush API turns the Card Rush shops (カードラッシュ, cardrush-pokemon.jp and its nine sister shops) into JSON in three actions.
3 active endpoints, on 2 and 3 credit tiers.
- POST/cardrush/v1/search
- POST/cardrush/v1/card
- POST/cardrush/v1/buying_prices
What Card Rush endpoints does ReefAPI ship?
3 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Card Rush API
3 of 3 endpoints, ready to run
Every product for a card name on one Card Rush shop: price, condition, grade and stock.
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
How the Card Rush API works
Card Rush 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 530 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.
Buy and sell spread for one card at Card Rush
Two calls, from a card name to what Card Rush pays for it and what it sells the same card for.
Every Pikachu on the buying list, highest buying price first, each with its card number, rarity and shop_product_id.
The shop product the buying row refers to: sale price in yen with tax, condition, stock.
The difference between Card Rush's buying price and its sale price for the same card, both in yen, read from the live shop.
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}'{
"ok": true,
"data": { … },
"meta": {
"api": "cardrush",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}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 title | field | value |
|---|---|---|
| 〔状態A-〕ピカチュウ【C】{033/087} | condition | A- |
| 〔状態B〕 / 〔状態C〕 | condition | B / C |
| 〔PSA10鑑定済〕ミュウ【-】{016/036} | graded, grader, grade | true, PSA, 10 |
| 【SAR】 / 【SEC】 / 【ウルトラ】 | rarity | SAR / SEC / ウルトラ |
| {025/165} / {OP13-118} | card_number | 025/165 / OP13-118 |
| [EX+]稲妻/Lightning Bolt《日本語》【A25】 (Magic) | condition, language, set_code | EX+, 日本語, A25 |
| ☆SALE☆ | on_sale | true (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).
What Card Rush publishes — measured 2026-10-15
Card Rush runs one web shop per game and a buying-price list per game. These are the numbers and limits measured on the live sites.
Ten: Pokémon (75,090 products listed), One Piece, Yu-Gi-Oh!, Magic: The Gathering, Duel Masters, Battle Spirits, Digimon, Vanguard, Dragon Ball Fusion World, Shadowverse: Evolve.
Price in yen with tax, web-shop stock, condition, PSA grade, rarity, card number, set code (Pokémon), language (Magic), image; card adds the most one order can take and the category.
Nine games. Pokémon 125 pages of 100 cards on 2026-10-15; buying price in yen, card number, rarity, set, updated time and the matching shop product.
10 to 100 rows per page on search, 1 to 100 on buying_prices; a page past the end returns no rows.
Price history, store (physical shop) stock, buying prices per condition, and an English card name outside Magic.
What people build with Card Rush
The jobs this data is most often used for.
endpoints
credits per call
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.
What Card Rush data costs
The cheapest call here is 2 credits, so $15/mo (Pro) buys 5,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 530 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/cardrush/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"ピカチュウ","per_page":20}'import requests
r = requests.post(
"https://api.reefapi.com/cardrush/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"query": "ピカチュウ",
"per_page": 20
},
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Card Rush.
Get a free key →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 PSA slabs (search PSA10 to list them).
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.
266 E-commerce & Marketplaces APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Card Rush, 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 529 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-10-15.