Check current access and terms
TCGPlayer's official getting-started documentation, checked on 7 November 2026, states that it is no longer granting new API access. Existing integrations remain subject to the provider's terms. Do not infer that existing credentials have stopped working or that every alternative has the same data contract.
For a dated comparison of providers, see our TCG API comparison. This article explains the TCGAPIs option and the checks needed before adopting it.
Match the API to your use case
Developers building TCG applications typically need a combination of:
- Catalog records, images and stable product identifiers.
- Product prices by printing, with source timestamps where available.
- Condition-specific SKU prices.
- Seller listings or reported sales, which are distinct from price guides.
- Source-specific marketplace records and clear currency definitions.
TCGAPIs provides these through separate endpoints. Coverage varies by game, product and source. There is no promise that every product has a price, a sale or an active listing.
Access by plan
Every monthly plan can call every endpoint. Catalog and price requests take 1 call; SKU-level prices and listing snapshots take 5 calls on Hobby and Business.
| Plan | General API allowance | Calls per request on a monthly plan |
|---|---|---|
| Hobby — £99/month | 20,000 calls/month | Catalog 1; product prices, sales history, historic prices and marketplace price data 1; SKU-level prices and TCGPlayer listing snapshots 5 |
| Business — £199/month | 50,000 calls/month | Catalog 1; product prices, sales history, historic prices and marketplace price data 1; SKU-level prices and TCGPlayer listing snapshots 5 |
| Unlimited — £499/month | No general call cap | Every request takes 1 call |
Recognition has a separate allowance: 1,000 calls on Hobby, 15,000 on Business and no recognition cap on Unlimited. New accounts receive 100 free credits for all customer data API endpoints. After your free credits are used, buy a credit pack (from £10, no subscription) or choose a monthly plan. See pricing for the current terms.
Authenticate with an API key
Send your TCGAPIs key in the x-api-key header. Keep it server-side; do not send it as a Bearer token or embed it in browser code.
const productId = process.env.TCGAPIS_PRODUCT_ID; // An ID verified against the catalog
const response = await fetch('https://api.tcgapis.com/api/v2/prices/' + productId, {
headers: { 'x-api-key': process.env.TCGAPIS_KEY },
});
const body = await response.json();
if (!response.ok || !body.success) throw new Error(body.error || 'Price request failed');
console.log(body.data.prices); // Records keyed by printing
console.log(body.data.last_updated); // May be missing or nullThis example costs 2 credits per request; on a monthly plan it takes 1 call. Select the correct printing and treat unavailable values as unavailable, not zero. TCGPlayer product prices are USD.
Important endpoint distinctions
| Endpoint | Purpose |
|---|---|
GET /api/v2/games | Public game/category discovery |
GET /api/v2/expansions/:categoryId | Catalog expansions |
GET /api/v2/cards/:groupId | Catalog cards in an expansion |
GET /api/v2/products/:productId | One product's catalog metadata |
GET /api/v2/prices/:productId | Product-price records by printing |
GET /api/v2/sales-history/:productId | Recent source sales under data.sales |
GET /api/v2/historic-prices/:productId | Daily source price snapshots |
GET /api/v2/livelistings/:productId | Available listing snapshot (1 call on Unlimited, 5 on Hobby and Business) |
List responses are envelopes with data and pagination fields, not bare arrays. Check each endpoint's documentation before reusing a parser from another provider.
Compare marketplace records carefully
Cardmarket price guides use EUR and their own idProduct identifiers. Cross-references to TCGPlayer IDs can be absent. Trend prices are a Magic-only provider layer; they are not a multi-game replacement for the separate Cardmarket or CardTrader routes.
Prices from different sources need not share currencies, printings, timestamps or methodology. The data-coverage reference explains those distinctions. Do not assume identical values or refresh cadence.
Plan a measured migration
Use your own verified product sample. Compare identifiers, response envelopes, field availability, pagination, errors and source timestamps. Handle quota errors and transient failures explicitly. Keep a rollback path until your application has passed those checks.
No availability or performance benchmark is claimed in this guide. Measure latency and error rates for your own workload instead of assuming that a provider never fails.
TCGAPIs is independent and is not affiliated with or endorsed by TCGPlayer or eBay. For an implementation walkthrough, see the migration guide and Pokemon tracker tutorial.
Get Your API Key
Explore catalog records across 60+ trading card games, with price, listing and sales-history data where available.
Start Building