One Piece TCG API Guide
Access One Piece TCG card, set, and sales data through the SilphCo Analytics API
Last updated:
Overview
SilphCo Analytics covers the One Piece TCG alongside Pokemon TCG. Shared public card, set, and sales endpoints accept a ?game= parameter to select which game's data to return. One Piece coverage includes eBay sales, pricing rollups, and TVWAP metrics (set/card counts grow as the catalog is refreshed — list them via the sets and cards endpoints).
New to the API? Start with the Getting Started guide for authentication and general API usage. This page covers One Piece–specific details.
The ?game= parameter
Every data endpoint accepts an optional game query parameter. Set it to onepiece to query One Piece data, or pokemon for Pokemon (the default).
Without the parameter, the API defaults to pokemon. Always pass ?game=onepiece explicitly in production integrations to avoid ambiguity.
# One Piece sets
curl "https://silphcoanalytics.xyz/api/v3/sets?game=onepiece" \
-H "Authorization: Bearer YOUR_API_KEY"
# Pokemon sets (default)
curl "https://silphcoanalytics.xyz/api/v3/sets?game=pokemon" \
-H "Authorization: Bearer YOUR_API_KEY"Set IDs
One Piece set IDs use a different format from Pokemon. The following prefixes identify each product line:
| Prefix | Description |
|---|---|
| OP01–OP17 | Main booster sets (Romance Dawn, Paramount War, …) |
| ST-29, ST-30 | Starter Deck EX series |
| SD01 | Set Sail Deck Set |
| EB-01–EB-03 | Extra Booster sets |
| LT-01 | Learn Together Deck Set |
| OP-PR | Promotion cards |
| OP-CS | Collection Sets |
| OP-DD | Demo Deck cards |
| OP-RP | Revision Pack cards |
Some sets have suffixes like OP16 RE (Release Event Cards) or composite IDs like OP15-EB04. The full list is available from the /api/v3/sets?game=onepiece endpoint.
Card IDs
One Piece card IDs are prefixed with op-. There are two ID formats depending on the product type:
| Format | Example | Used for |
|---|---|---|
| op-{set_id}-{card_number} | op-OP01-064 | Individual cards (primary format from sets endpoint) |
| op-{product_id} | op-498735 | Booster boxes, cases, and sealed products |
Both formats are accepted by all card endpoints. The op- prefix distinguishes One Piece cards from Pokemon cards, which use {set_id}-{number} IDs (e.g. base1-4, me2pt5-276).
# Look up a specific One Piece card (set-card_number format)
curl "https://silphcoanalytics.xyz/api/v3/cards/op-OP01-064?game=onepiece" \
-H "Authorization: Bearer YOUR_API_KEY"
# Look up a sealed product (product_id format)
curl "https://silphcoanalytics.xyz/api/v3/cards/op-498735?game=onepiece" \
-H "Authorization: Bearer YOUR_API_KEY"Example requests
List all One Piece sets
curl "https://silphcoanalytics.xyz/api/v3/sets?game=onepiece&limit=5" \
-H "Authorization: Bearer YOUR_API_KEY"Search for Luffy cards
curl "https://silphcoanalytics.xyz/api/v3/search?q=luffy&game=onepiece&limit=10" \
-H "Authorization: Bearer YOUR_API_KEY"Cards in a set (filter)
# Cards filtered by set via the cards list (no global /sales firehose)
curl "https://silphcoanalytics.xyz/api/v3/cards?game=onepiece&set_id=OP01&limit=10" \
-H "Authorization: Bearer YOUR_API_KEY"Per-card sales
curl "https://silphcoanalytics.xyz/api/v3/cards/op-OP01-064/sales?game=onepiece&limit=10" \
-H "Authorization: Bearer YOUR_API_KEY"Card market history
curl "https://silphcoanalytics.xyz/api/v3/cards/op-OP01-064/market-history?game=onepiece" \
-H "Authorization: Bearer YOUR_API_KEY"Available endpoints
All endpoints below accept the ?game=onepiece query parameter (same public routes as Pokemon). See the API Reference for full parameter details.
| Method | Endpoint | Description |
|---|---|---|
| GET | /api/v3/cards?game=onepiece | List One Piece cards with pricing and set info |
| GET | /api/v3/cards/{id}?game=onepiece | Card detail with full rollup metrics |
| GET | /api/v3/sets?game=onepiece | List all One Piece sets with volume/sales |
| GET | /api/v3/sets/{id}?game=onepiece | Set detail with aggregated stats |
| GET | /api/v3/search?game=onepiece | Full-text search within One Piece cards |
| GET | /api/v3/lookup?game=onepiece | Resolve a card or set identifier |
| GET | /api/v3/trending?game=onepiece | Trending One Piece cards |
| GET | /api/v3/cards/{id}/sales?game=onepiece | Sales history for a specific card |
| GET | /api/v3/cards/{id}/market-history?game=onepiece | Daily market history for a card |
| GET | /api/v3/cards/{id}/price-history?game=onepiece | Graded oracle price history for a card |
Differences from Pokemon
Card IDs
One Piece cards use op- prefixed IDs with two formats: op-{set_id}-{card_number} for individual cards (e.g. op-OP01-064) and op-{product_id} for sealed products (e.g. op-498735). Pokemon cards use {set_id}-{number} (e.g. me2pt5-276).
Set IDs
One Piece uses alphanumeric set codes (OP01, ST-30, SD01) vs Pokemon set codes such as base1 and swsh12pt5.
Grading data
PSA/BGS/CGC grading population data is currently Pokemon-only. One Piece cards still show raw sales, TVWAP, and volume metrics — graded-slot fields will be null for OP cards until population data is ingested.
Languages
One Piece catalog data covers English and Japanese sets (?language=en or ?language=ja). Pokemon supports English, Japanese, and Simplified Chinese.
Data coverage
One Piece sales data comes from eBay. Pokemon additionally includes on-chain marketplace sales (Courtyard, Beezie, Renaiss, etc.). On-chain coverage for One Piece may expand in the future.