Yuyu-Tei APIyuyu-tei.jp ↗
Search and list One Piece card game prices from Yuyu-Tei. Get card codes, names, rarity, stock, and pricing across all sets via 2 endpoints.
What is the Yuyu-Tei API?
The Yuyu-Tei API gives developers structured access to One Piece card game single-card pricing data from yuyu-tei.jp across 2 endpoints. The search_cards endpoint accepts a card code like OP01-001 or a Japanese card name and returns per-card objects containing price, stock availability, rarity classification, set version, and image URL. The get_all_cards endpoint pages through the full inventory when at least one filter — rarity, version, or card type — is supplied.
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=%E3%82%B7%E3%83%A3%E3%83%B3%E3%82%AF%E3%82%B9' \ -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 and list card prices."""
from parse_apis.Yuyu_Tei_One_Piece_Card_Game_API import YuyuTei, Rarity, CardType, CardNotFound
client = YuyuTei()
# List all cards from a specific set
for card in client.cards.list(version="op01", limit=3):
print(card.card_name, card.rarity, card.price, "JPY", "| in stock:", card.in_stock)
# Search by card name with rarity filter
shanks = client.cards.search(search_word="シャンクス", rarity=Rarity.P_SEC, limit=3).first()
if shanks:
print(shanks.card_code, shanks.card_name, shanks.price_text, "version:", shanks.version)
# List by card type — only Character cards
for card in client.cards.list(card_type=CardType.CHARACTER, rarity=Rarity.SEC, limit=3):
print(card.card_code, card.card_name, card.price_text)
# Handle not-found errors on search
try:
result = client.cards.search(search_word="NONEXIST999", 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.list / cards.search / 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
Endpoints and Data Coverage
The search_cards endpoint is the primary lookup tool. Pass search_word as a card code (e.g. OP01-001, ST01-012) or a Japanese name (e.g. ルフィ, ゾロ) and receive an array of matching card objects. Each object includes card_code, card_name, rarity, price (integer), price_text (formatted string), stock (quantity), in_stock (boolean), version, image_url, and card_url. Optional parameters rarity, version, and card_type narrow results at the source; omitting them returns all matches across rarities and sets.
Browsing Full Inventory
The get_all_cards endpoint requires at least one of rarity, version, or card_type. Version codes follow Yuyu-Tei's naming convention: op01 through op16 for main sets, st01 and similar for starter decks, eb01 for extra boosters, and promo-op10 for promotional cards. Results are paginated using a 1-based page parameter. The response includes total_results (count of cards on the current page), the active filter values, and the same card object shape as search_cards.
Rarity Classifications
Cards are grouped under Yuyu-Tei's rarity tiers: P-SEC, SEC, SR, R, UC, C, and L, among others. The rarity field on each card object reflects the tier assigned by the source. Filtering by rarity is available on both endpoints, making it straightforward to, for example, pull all SEC-rarity cards from a specific set by combining rarity and version on get_all_cards.
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 price movements on specific One Piece cards by polling
search_cardswith a card code and storingpriceover time. - Build a collection valuation tool that looks up each card in a user's list by
card_codeand sums thepricefield. - Identify in-stock SEC and SR singles from a given set by filtering
get_all_cardswithrarity=SECand aversioncode. - Populate a card database with image URLs and Japanese names by iterating
get_all_cardsacross all set versions. - Alert users when a specific card comes back in stock by checking the
in_stockboolean fromsearch_cardson a schedule. - Compare Yuyu-Tei prices against other sources by exporting the
priceandcard_codefields for a full set.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Yuyu-Tei offer an official developer API?+
What does the `version` parameter accept, and where do I find valid values?+
version parameter takes Yuyu-Tei's internal set codes. Main booster sets use codes like op01 through op16; starter decks use codes like st01; extra boosters use codes like eb01; promotional releases use codes like promo-op10. If you omit version, both endpoints return cards across all sets.Does `total_results` in `get_all_cards` reflect the full dataset or just the current page?+
total_results is the count of cards returned on the current page, not a global count across all pages. To determine the full set size, paginate through all pages and sum each page's total_results.Does the API cover card condition grades (e.g. near-mint vs. played)?+
price and stock per card object; condition-grade pricing is not broken out in the response. You can fork this API on Parse and revise it to add a condition-grade breakdown if Yuyu-Tei surfaces that data for the cards you need.