Stop Maintaining Mapping Tables: Direct Scryfall, MTGJSON, and TCGplayer SKU Lookups Are Here

If you’re building a Magic: The Gathering application, there’s a good chance your database was initialized using recognized standards like Scryfall or MTGJSON. They are fantastic resources for card text, artwork, and rulings.

But when it came time to pull lightning-fast, reliable market pricing, you hit a common snag: The Mapping Problem.

You had to fetch our data, build a complex translation table to match our internal cardId with your existing Scryfall IDs, and keep that table updated as new sets were released. It worked, but it was bloat. And, we hate bloat.

We believe JustTCG should fit seamlessly into your stack, not force you to rebuild it. That’s why, heavily requested by our community, we’ve just deployed a major quality-of-life update to our /cards endpoint.

Native Support for Major TCG Standards #

Starting today, you can query the JustTCG API directly using the identifiers you already have in your database. No intermediate mapping required.

We have added support for three new query parameters:

• scryfallId (for our MTG developers using Scryfall as their base truth)
• mtgjsonId (standard UUIDs for MTGJSON implementations)
• tcgplayerSkuId (perfect for stores managing inventory down to the specific variant/condition level)

How It Works #

It’s simple. If you have a Scryfall ID for “Black Lotus” and just need the current market price, you no longer need to look up our internal ID first. Just ask for it directly.

Before (The Old Way):

1. Query our API to find the JustTCG cardId that matches your Scryfall ID.
2. Store that mapping.
3. Query pricing using the cardId.

Now (The JustTCG Way):

GET https://api.justtcg.com/v1/cards?scryfallId=4a2e428c-dd25-484c-bbc8-2d6ce10ef42c

Our backend handles the resolution instantly, returning the same comprehensive pricing data you expect, right alongside the external IDs you provided.

Smart Precedence #

Because we know real-world data can get messy, we’ve implemented strict precedence logic to ensure you always get a deterministic result. If you accidentally send multiple identifiers in one request, we prioritize the most specific one first (e.g., a specific JustTCG variantId or tcgplayerSkuId will take priority over a broader card-level ID).

A Note on Data Quality #

To maintain the reliability you expect, our ingestion pipeline only indexes cards once they meet our pricing data thresholds. You may notice a slight delay for brand-new sets or ultra-rare cards while enough sales history accumulates to generate a statistically significant market price. We prefer to return no data rather than bad data.

Ready to Simplify Your Codebase? #

This feature is live right now. You can rip out those old mapping tables and start fetching cleaner, faster data today.

Check out the updated API Documentation for the full technical breakdown of these new parameters.

Keep building amazing things!