Which One Piece API? OPTCG API, API TCG & Live Prices

One Piece is the third-biggest trading card game on TCGPlayer by sales volume, behind only Magic and Pokemon. It is also the one with the thinnest developer tooling — there is no Scryfall for One Piece, and the APIs that do exist were mostly built by one person in their spare time.

This guide covers the One Piece Card Game APIs worth knowing in 2026, what each does well, where each falls short, and how to pick the right one.

Why One Piece Is Harder Than It Looks

One Piece launched in late 2022, so the card pool is small compared to Magic or Yu-Gi-Oh!. That makes it sound easy. It isn’t, for three reasons.

Parallel art is the whole market. Almost every meaningful card has a regular printing and one or more alternate-art parallels, and the gap between them is enormous. Take Donquixote Doflamingo from Romance Dawn: the base leader trades around $0.31, while the parallel version of the same card sits at roughly $261. Same card name, same set, same card number — an 800x price difference. If your data model has one price per card, it is wrong for One Piece specifically.

The set structure is messy. Sets are not a clean OP-01 through OP-16 sequence. There are numbered main sets, Extra Boosters that carry their own dual codes like OP15-EB04, Premium Boosters (PRB-01, PRB-02), starter decks, promo waves, and Don!! cards. Any API that models sets as a simple numbered list will quietly drop a chunk of the catalog.

English and Japanese are separate markets. The Japanese release runs months ahead of English, and prices diverge sharply. Most One Piece APIs cover the English release only.

Common use cases:

• Deck builders — Card search, card text, colors, costs, Don!! curve
• Collection managers — Track base vs. parallel printings separately
• Price trackers — Monitor market values, catch reprint and rotation swings
• Store tools — Inventory pricing, buylist generation
• Meta analytics — Leader win rates cross-referenced with card prices

OPTCG API

OPTCG API is the closest thing One Piece has to a community standard, and it is free and unauthenticated.

What it offers:

• Full card data — card text, color, type, cost, power, counter, life, attribute, sub-types
• Hosted card images
• Base and parallel printings returned as separate rows, each with its own price
• market_price and inventory_price fields, refreshed daily
• A date_scraped field on every row, so you can check freshness yourself rather than trusting the cadence
• Roughly two weeks of price history viewable on the site
• No authentication required
• Separate endpoints for set cards, starter decks, promos, and Don!! cards

Limitations:

• English release only — no Japanese pricing
• Covers 21 set groupings (OP-01 through OP-16 plus extra and premium boosters, starter decks, and promos), so sealed product and some smaller groupings are out of scope
• Only about two weeks of price history, which is not enough for trend analysis
• Runs on a personal VPS with no formal rate limit or uptime guarantee — the maintainer explicitly asks users not to hammer it
• One Piece only

Best for: Deck builders and card search tools, plus lightweight price lookups where a two-week window is enough.

// OPTCG API: one card, all printings (no auth required)
const res = await fetch('https://optcgapi.com/api/sets/card/OP01-060/');
const cards = await res.json();

cards.forEach(c => {
  console.log(`${c.card_name} [${c.rarity}] — $${c.market_price}`);
});
// Donquixote Doflamingo (060) [L] — $0.31
// Donquixote Doflamingo (060) (Parallel) [L] — $261.28

API TCG

API TCG is a multi-game card database covering One Piece alongside Pokemon, Digimon, Magic, Gundam, Union Arena, and others.

What it offers:

• Consistent response shape across every game it covers, which is genuinely useful if you are building multi-game
• Card metadata and images for One Piece
• Query by name and other card attributes
• Free registration for an API key

Limitations:

• Requires an API key via the x-api-key header — you need to register at apitcg.com/platform
• Card-metadata focused; it is not a market pricing source
• No price history
• Documentation is sparse compared to the alternatives

Best for: Multi-game apps that need consistent card metadata and images and get pricing from somewhere else.

// API TCG: search One Piece cards by name
const res = await fetch(
  'https://apitcg.com/api/one-piece/cards?name=Luffy',
  { headers: { 'x-api-key': process.env.APITCG_KEY } }
);
const data = await res.json();

Bandai’s Official Card List

Bandai runs the official English card list, but it is a website, not an API. There is no documented JSON endpoint, no rate limit policy, and no stability guarantee.

What it offers:

• Authoritative card text, errata, and rulings
• New set spoilers published here first
• Official ban and restriction announcements

Limitations:

• No public API. Anything you build against it is scraping, and it can break without notice
• No pricing whatsoever
• HTML parsing required, and the markup changes between set releases

Best for: Nothing you plan to ship. Use it as a source of truth to check against, not as a dependency.

TCG API

TCG API covers the gap the others leave: real market pricing at the printing level, with real history, across One Piece and 53 other games.

What it offers:

• Real market prices sourced from TCGPlayer, refreshed daily for One Piece
• 87 One Piece sets and 7,367 cards — including starter decks, promos, Don!! cards, and sealed product, not just numbered booster sets
• Normal and Foil prices tracked separately per printing
• Price change data over 24h, 7d, and 30d, returned as percentages
• Per-condition price floors (Near Mint through Damaged) from live listings
• Full historical price data for trend analysis, not just a two-week window
• Full-text search that matches card numbers like OP01-060 as well as names
• Bulk endpoints for pricing up to 500 cards in one request

Limitations:

• Card metadata is pricing-oriented — no card text, colors, costs, or Don!! values
• No hosted card images (returns TCGPlayer product image URLs)
• English/TCGPlayer market only — no Japanese pricing
• Requires an API key (free tier: 100 requests/day)

Best for: Price tracking, collection valuation, store inventory tools, and anything multi-game.

// TCG API: search One Piece cards, one row per printing
const API_KEY = 'your-api-key';
const res = await fetch(
  'https://api.tcgapi.dev/v1/search?q=OP01-060&game=one-piece-card-game&per_page=5',
  { headers: { 'X-API-Key': API_KEY } }
);
const data = await res.json();

data.data.forEach(card => {
  console.log(`${card.name} — ${card.set_name} [${card.rarity}]`);
  console.log(`  ${card.printing}: $${(card.market_price ?? 0).toFixed(2)}`);
});

Note the auth header: TCG API uses X-API-Key, not an Authorization: Bearer token.

Search returns flat rows — one per printing — each with its own rarity and price, which is exactly the shape One Piece needs given how far parallels diverge from base printings. To get every printing of a single card with its 24h/7d/30d changes, call /v1/cards/{id}/prices, which returns an array of price rows.

Feature Comparison

Card Data & Search

• OPTCG API — Excellent. Full card text, color, cost, power, counter, sub-types
• API TCG — Good. Consistent shape across games, lighter on detail
• Bandai official — Authoritative but not machine-readable
• TCG API — Pricing-focused. Search by name, card number, set, rarity, and price

Card Images

• OPTCG API — Hosted, free
• API TCG — Hosted
• Bandai official — Available but scraping-only
• TCG API — Links to TCGPlayer product images

Base vs. Parallel Printings

• OPTCG API — Separate rows with separate prices
• API TCG — Separate cards, no pricing
• Bandai official — Listed, no pricing
• TCG API — Separate rows per printing, with per-condition floors

Pricing

• OPTCG API — Daily market price, ~2 weeks of history
• API TCG — Not a pricing source
• Bandai official — None
• TCG API — Daily market prices per printing, with 24h/7d/30d changes and full history

Multi-Game Support

• OPTCG API — One Piece only
• API TCG — One Piece, Pokemon, Digimon, Magic, Gundam, Union Arena, and more
• Bandai official — One Piece only
• TCG API — 54 games (Pokemon, Magic, Yu-Gi-Oh!, Lorcana, etc.)

When to Use Each

Use OPTCG API when you need card text, colors, costs, and images for a deck builder, and a rough daily price is good enough. It is free, it needs no key, and it models parallels correctly. Be a good citizen about request volume.

Use API TCG when you are already building across several games and want one consistent card-metadata shape for all of them.

Use TCG API when money is part of your product — collection valuation, price alerts, store pricing, or anything that needs to know what a specific parallel is actually worth today and what it was worth last month.

Use two together. This is the setup most One Piece developers land on: OPTCG API or API TCG for card identity, text, and images, TCG API for what each printing costs over time. They complement each other cleanly, and neither duplicates the other’s strengths.

Example: Tracking Parallel Art Spikes

Because One Piece parallels move so violently around set releases and meta shifts, the most useful thing you can build is a watchlist of what just spiked. The price movers endpoint does this in one call:

const API_KEY = 'your-api-key';

async function findSpikes() {
  const res = await fetch(
    'https://api.tcgapi.dev/v1/prices/top-movers?game=one-piece-card-game&direction=up&period=7d&limit=20',
    { headers: { 'X-API-Key': API_KEY } }
  );
  const data = await res.json();

  console.log('Biggest 7-day gains in One Piece:\n');
  data.data.forEach((card, i) => {
    console.log(
      `${i + 1}. ${card.name} (${card.set_name}) [${card.printing}] ` +
      `$${card.market_price.toFixed(2)} — ${card.price_change}%`
    );
  });
}

findSpikes();

price_change is a percentage, not a dollar amount. Use direction=down to catch crashes instead, period accepts 24h, 7d, or 30d, and limit caps out at 50.

Run that weekly and you have a One Piece market feed with no scraping and no manual tracking.

Getting Started

For a deeper dive:

• Quickstart Guide — Make your first API call in 2 minutes
• Search API Reference — Full-text search with filters
• Price Data — Price endpoints and movers
• One Piece on TCG API — All 87 sets and card data
• Yu-Gi-Oh! API Guide — YGOPRODeck and the Yu-Gi-Oh! landscape
• Trading Card Game APIs Compared — Every major TCG API side by side

Ready to add pricing to your One Piece project? Sign up for a free TCG API key and follow the quickstart guide. The free tier gives you 100 requests per day, and paid plans start at $9.99/month.

Questions about choosing the right API? Join us on Discord — we’re happy to help you figure out the best stack for your project.