Separate identity, prices and stock
Catalog data tells you which card a record describes. Price endpoints supply source price records. Neither automatically knows your physical stock or the rules you want to apply to your shop.
Before automating updates, verify each shop SKU's mapping to a product, printing, language and condition. Hold ambiguous mappings for review. Start with a dry-run report rather than publishing changes directly.
Choose the appropriate plan
| Workflow | Calls per request on a monthly plan | Considerations |
|---|---|---|
| Catalog lookup and product identifiers | 1 call on every plan | Catalog availability and monthly requests |
| Product-level price records | 1 call on every plan | Hobby's 20,000 calls cover up to 20,000 price requests a month |
| SKU condition prices or listing snapshots | 1 call on Unlimited, 5 on Hobby and Business | Correct SKU mapping and source timestamps |
Every monthly plan can call every endpoint, so plan choice depends on how many calls your requests take, not just inventory size. Five thousand individual price requests each day would exceed Business's 50,000 calls per month. Budget discovery calls and refreshes, and use documented bulk or export routes only where they support the data you need.
Produce a review report
This example calculates suggested product-level prices from verified product IDs. It deliberately does not update a marketplace or your inventory.
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 || 'API request failed');
return body;
}
const productIds = JSON.parse(process.env.VERIFIED_PRODUCT_IDS || '[]');
const suggestions = [];
for (const productId of productIds) {
if (!Number.isSafeInteger(productId) || productId <= 0) continue;
const body = await get('/prices/' + productId);
const record = body.data?.prices?.Normal; // Only for mappings verified as this printing
const market = record?.marketPrice;
if (typeof market !== 'number' || !Number.isFinite(market)) {
suggestions.push({ productId, status: 'hold', reason: 'Price unavailable' });
continue;
}
suggestions.push({
productId, currency: 'USD', sourceUpdatedAt: body.data.last_updated ?? null,
sourceMarket: market,
suggestedPrice: Math.round(market * 1.10 * 100) / 100, // Example policy, not a recommendation
status: 'review',
});
}
console.log(JSON.stringify(suggestions, null, 2));A product-level price is not a substitute for a condition-specific SKU price. If your stock is defined by condition, use the appropriate SKU endpoint; each request takes 1 call on Unlimited and 5 on Hobby and Business. Keep source currencies explicit; a Cardmarket EUR guide must not be treated as a USD price.
Add operational safeguards
Set your own minimums, fees, rounding and change thresholds. Skip stale or unavailable records according to an explicit policy. Review unusually large changes. Keep a before/after record and reconcile the provider response before retrying an update that may already have succeeded.
Stock synchronization is a separate integration. Do not infer quantity from price records, and do not change inventory as a side effect of a price lookup.
Measure the result
This guide does not claim measured savings or revenue gains. Compare your baseline with the new process: review time, ambiguous mappings, missing prices, rejected updates and realised outcomes. A larger number of automated changes is not itself evidence of better pricing.
See the pricing reference, SKU pricing and API documentation for the current data contracts.
Get Your API Key
Explore catalog records across 60+ trading card games, with price, listing and sales-history data where available.
Start Building