Yuyu-Tei APIyuyu-tei.jp ↗
Search One Piece card game single prices from Yuyu-Tei. Get price, stock status, rarity, and card variant data by card code or Japanese name.
What is the Yuyu-Tei API?
The Yuyu-Tei One Piece Card API provides access to single card pricing data from yuyu-tei.jp through 1 endpoint returning up to 10 response fields per card. The search_cards endpoint accepts a card code like OP01-001 or a Japanese card name and returns current prices, stock availability, rarity classifications, and set version information for matching cards.
curl -X GET 'https://api.parse.bot/scraper/1d31f593-ebaf-4791-a047-2c9751946cee/search_cards?rarity=P-SEC&version=op01&card_type=%E3%82%AD%E3%83%A3%E3%83%A9%E3%82%AF%E3%82%BF%E3%83%BC&search_word=OP01-001' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace yuyu-tei-jp-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: YuyuTei One Piece Card Game — search prices by code and name."""
from parse_apis.yuyu_tei_jp_api import YuyuTei, Rarity, CardType, CardNotFound
client = YuyuTei()
# Search by card code — returns all variants (parallel, standard, promo)
for card in client.cards.search(search_word="OP01-001", limit=5):
print(card.card_name, card.rarity, card.price, "JPY", "| in stock:", card.in_stock)
# Search by name with rarity filter — only Super Rare Luffy cards
luffy_sr = client.cards.search(search_word="ルフィ", rarity=Rarity.SR, limit=3).first()
if luffy_sr:
print(luffy_sr.card_code, luffy_sr.card_name, luffy_sr.price_text, "version:", luffy_sr.version)
# Filter by card type — search Leader cards only
for leader in client.cards.search(search_word="シャンクス", card_type=CardType.LEADER, limit=3):
print(leader.card_code, leader.card_name, leader.rarity, leader.price_text)
# Handle not-found errors
try:
result = client.cards.search(search_word="OP01-001", rarity=Rarity.P_SEC, limit=1).first()
if result:
print(result.card_name, result.price)
except CardNotFound as exc:
print(f"No cards found: {exc.search_word}")
print("exercised: cards.search (by code / by name + rarity / by name + card_type / error handling)")
Search One Piece card game single card prices by card code or name. Results are grouped by rarity (P-SEC, SEC, SR, R, UC, C, L, etc.) and include price, stock availability, and card variant information. Each result includes the card's rarity classification and version/set origin.
| Param | Type | Description |
|---|---|---|
| rarity | string | Filter results by card rarity. Omitting returns all rarities. |
| version | string | Filter by card set/version code (e.g. op01, op16, st01, eb01, promo-op10). Omitting returns all versions. |
| card_type | string | Filter results by card type. Omitting returns all types. |
| search_wordrequired | string | Card code (e.g. OP01-001, ST01-012) or card name in Japanese (e.g. ルフィ, ゾロ). |
{
"type": "object",
"fields": {
"cards": "array of card objects with card_code, card_name, rarity, price, price_text, stock, in_stock, version, image_url, card_url",
"search_word": "string",
"rarity_filter": "applied rarity filter or null",
"total_results": "integer",
"version_filter": "applied version filter or null",
"card_type_filter": "applied card type filter or null"
},
"sample": {
"data": {
"cards": [
{
"price": 34800,
"stock": 2,
"rarity": "P-L",
"version": "op01",
"card_url": "https://yuyu-tei.jp/sell/opc/card/op01/10002",
"in_stock": true,
"card_code": "OP01-001",
"card_name": "ロロノア・ゾロ(パラレル)",
"image_url": "https://card.yuyu-tei.jp/opc/100_140/op01/10002.jpg",
"price_text": "34,800 円"
},
{
"price": 120,
"stock": 3,
"rarity": "L",
"version": "op01",
"card_url": "https://yuyu-tei.jp/sell/opc/card/op01/10001",
"in_stock": true,
"card_code": "OP01-001",
"card_name": "ロロノア・ゾロ",
"image_url": "https://card.yuyu-tei.jp/opc/100_140/op01/10001.jpg",
"price_text": "120 円"
}
],
"search_word": "OP01-001",
"rarity_filter": null,
"total_results": 4,
"version_filter": null,
"card_type_filter": null
},
"status": "success"
}
}About the Yuyu-Tei API
What the API Returns
The search_cards endpoint queries Yuyu-Tei's One Piece card inventory and returns an array of card objects. Each object includes card_code, card_name, rarity, price, price_text, stock, in_stock, version, image_url, and card_url. The in_stock boolean makes it straightforward to filter out unavailable cards without parsing stock strings manually. Prices reflect the shop's current listed sell price for individual cards.
Filtering Options
Four input parameters control what search_cards returns. search_word is the only required field and accepts either a card code (e.g. ST01-012) or a Japanese card name (e.g. ルフィ). Optional filters rarity, version, and card_type narrow results further. The version parameter accepts set codes such as op01, op16, st01, eb01, or promo-op10. Omitting any optional parameter returns results across all values for that dimension. When multiple printings of a card exist, each appears as a separate result with its own rarity and version fields.
Rarity and Set Coverage
Cards are grouped by rarity tiers used by the One Piece Card Game: P-SEC, SEC, SR, R, UC, C, L, and others. The version field maps each card to its source set, covering main booster sets (op01–op16), starter decks (st-prefix), and promotional sets. This allows price comparison across different printings of the same card character.
The Yuyu-Tei API is a managed, monitored endpoint for yuyu-tei.jp — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when yuyu-tei.jp 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 yuyu-tei.jp 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 current sell prices for high-rarity SEC and P-SEC One Piece cards across booster sets
- Check real-time stock availability using the
in_stockfield before placing an order - Compare prices across multiple printings of a card by filtering with different
versioncodes - Build a price alert tool that monitors
pricechanges for a watchlist of card codes - Aggregate rarity-tier pricing data across a full set by querying all cards with a shared
versionfilter - Look up card image URLs and shop links by card code for use in a collection tracker or Discord bot
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Yuyu-Tei have an official developer API?+
What does the search_cards endpoint return when a card has multiple printings?+
cards array, with its own rarity, version, price, and in_stock values. You can distinguish them by their card_code or version field, since the same character may appear in multiple sets.Does the API cover buy prices or trade-in rates, not just sell prices?+
price, price_text) for individual card listings. Buy/trade-in prices that Yuyu-Tei offers for cards are not included in the response. You can fork this API on Parse and revise it to add an endpoint covering buy price data.Can I search using English card names?+
search_word parameter accepts card codes in standard format (e.g. OP01-001) or Japanese card names. Yuyu-Tei is a Japanese shop and its catalog uses Japanese names, so English-name searches are not reliably matched. Card codes are the most predictable way to look up a specific card.