Skip to content
TTCGAPIs
guides5 min read

TCGPlayer API Migration: IDs, Authentication and Price Responses

Migrate a TCGPlayer integration to TCGAPIs by checking identifiers, changing authentication, and adapting to separate product, pricing and listing responses.

T

TCGAPIs Team

Updated

Start with the API contract

Moving between providers requires more than replacing a hostname. TCGAPIs uses TCGPlayer identifiers for TCGPlayer-sourced catalog records, but authentication, response envelopes, endpoint access and freshness must be checked separately. The route implementation was reviewed on 7 November 2026; the signup-credit offer was updated on 9 November 2026. It does not promise identical data, refresh timing or a fixed migration duration.

TCGPlayer's official getting-started documentation describes access and authentication for its API. Check those terms if you maintain an existing integration. TCGAPIs is independent of TCGPlayer.

1. Check identifiers before changing requests

For TCGPlayer-sourced records, categoryId, groupId, productId and skuId retain their respective meanings. Resolve a product in the TCGAPIs catalog before relying on an old mapping. A missing record or variant should be handled explicitly, not replaced with a different printing.

Other provider identifiers are separate. In particular, Cardmarket idProduct is not interchangeable with TCGPlayer productId. Cross-references can be missing. The Cardmarket guide explains its identifier chain and EUR price-guide fields.

2. Change authentication

TCGPlayer's client-credentials flow uses a bearer token. Protected TCGAPIs data requests use your API key in x-api-key. Keep production keys on your server.

Previous provider example — TCGPlayer:

curl 'https://api.tcgplayer.com/v1.39.0/pricing/product/TCGPLAYER_PRODUCT_ID' \
  -H 'Authorization: Bearer TCGPLAYER_TOKEN'

TCGAPIs example:

curl 'https://api.tcgapis.com/api/v2/products/TCGPLAYER_PRODUCT_ID' \
  -H 'x-api-key: YOUR_API_KEY'

Replace the placeholder with a verified product ID. This second request returns catalog details; product prices are a separate endpoint.

3. Adapt the response envelope

Do not keep a parser that assumes response.data[0].marketPrice without checking the new contract. A TCGAPIs product-price response contains pricing records under data.prices, grouped by printing. The record timestamp is data.last_updated when available. A catalog response and a pricing response are not one combined object.

The following runnable example searches for a Magic card, takes the returned ID, and reads the separate envelopes. It requests product prices, which cost 2 credits per request; on a monthly plan they take 1 call.

const headers = { 'x-api-key': process.env.TCGAPIS_KEY };
async function get(path) {
  const response = await fetch('https://api.tcgapis.com/api/v2' + path, { headers });
  const body = await response.json();
  if (!response.ok || !body.success) throw new Error(body.error || 'Request failed');
  return body;
}
 
// Magic is category 1; discover categories with GET /api/v2/games.
const found = await get('/search?q=Lightning+Bolt&game=1&limit=1');
const productId = found.data[0]?.productId;
if (!productId) throw new Error('No matching product');
 
const product = await get('/products/' + productId);
const prices = await get('/prices/' + productId);
console.log(product.data);
console.log(prices.data.prices);
console.log(prices.data.last_updated);

Select the intended set and printing in a real application. The first search result is an example of identifier discovery, not proof that a particular printing is correct. Treat missing prices as unavailable rather than zero.

4. Use marketplace data within its scope

The trend-prices layer contains Magic: The Gathering snapshots. It is not a multi-marketplace price endpoint for every trading card game. Supported data providers include Cardkingdom, Manapool, Cardhoarder, Cardmarket and TCGPlayer, with availability depending on the record. Cardsphere is a recognized filter value with no ingested rows; Cardtrader is a separate endpoint family, not a trend-provider value.

For a Magic product that has a mapping into this layer:

const trends = await get('/trendprices/' + productId);
console.log(trends.data); // Array of snapshot rows, not a providers object

Read each row's provider, currency, printing, retail/buylist type and timestamp before comparing amounts. The API does not guarantee identical values or refresh timing across providers. See the data-coverage reference for source distinctions.

5. Select the right endpoint and plan

Every monthly plan can call every endpoint. The plans differ in their allowances and in how many calls a request takes:

  • Hobby: 20,000 general API calls per month, plus 1,000 recognition calls. Catalog, price and history requests take 1 call, SKU prices and listings 5.
  • Business: 50,000 general API calls per month, plus 15,000 recognition calls. Prices and history take 1 call, SKU prices and listings 5.
  • Unlimited: no general API or recognition cap, and every request takes 1 call.

The current pricing page is the source for subscription terms. New accounts receive 100 free credits for all customer data API endpoints; they do not provide unlimited use. After your free credits are used, buy a credit pack (from £10, no subscription) or choose a monthly plan.

For listings, use /api/v2/livelistings/{productId}; a request takes 1 call on Unlimited and 5 on Hobby and Business. These can be cached for up to an hour; a stored snapshot may be returned when the source is unavailable. For sales history and daily historic prices, use their separate documented endpoints; a request takes 1 call. Neither endpoint is a complete record of every market transaction.

6. Validate before switching production

Test your actual products and printings. Check pagination, missing IDs, absent prices, timestamps, currency, error envelopes, and allowance and credit limits. Compare samples with your current integration without assuming exact equivalence. Keep a rollback path for your application until those checks pass.

The API documentation contains the current endpoint reference. The card recognition demo is useful if your integration starts from photographs instead of existing product IDs.

Get Your API Key

Explore catalog records across 60+ trading card games, with price, listing and sales-history data where available.

Start Building
TCGPlayer APIAPI migrationTCG datadeveloper guideREST API