API Updates

Fine-Tune Your Fetches: Announcing Multi-Condition & Multi-Printing Filters

At JustTCG, we're dedicated to a simple promise: providing the most reliable, developer-friendly TCG pricing API on the market. Part of that promise means we're obsessed with removing friction and doing the heavy lifting so you don't have to.

JustTCG Editor
August 6, 2025
3 minute read
449 views

Share this article

Fine-Tune Your Fetches: Announcing Multi-Condition & Multi-Printing Filters

Following our last Quality of Life update that introduced API-level sorting, we heard your feedback loud and clear. You wanted more power and more control over your API calls.

Today, we're delivering.

You can now filter by multiple card conditions or multiple printings in a single API request.

query-example

No more chaining multiple requests together. No more client-side logic to merge arrays. Just one clean, efficient call to get the exact data you need.

The Old Way: More Calls, More Code

Let's be honest, the old workflow was a bit of a grind. If you wanted to price-check both the Near Mint and Lightly Played versions of a card for your e-commerce store, you had to make two separate API calls:

  1. A GET request for condition=near-mint.
  2. A second GET request for condition=lightly-played.
  3. Then, you'd have to write code to combine the results in your application.

It worked, but it wasn't elegant. It meant more code for you to maintain, more of your rate limit used, and a slight delay for your users. We knew we could do better.

The New Way: Powerful, Comma-Separated Filters

We've supercharged the condition and printing query parameters. They now accept multiple comma-separated values, letting you bundle your logic into a single, lightning-fast request.

**Example 1: Fetching Multiple Conditions**

Need to grab both near-mint and lightly-played prices for a Pokémon card? It's as simple as this:

# Request both Near Mint and Lightly Played conditions at once
curl "https://api.justtcg.com/v1/cards?tcgplayerId=12345&condition=near-mint,lightly-played" \
  -H "x-api-key: YOUR_API_KEY"

The API response will now contain variants matching either of those conditions. Simple, clean, and efficient.

**Example 2: Fetching Multiple Printings**

The same power applies to card printings. Want to compare the prices for the Normal, Foil, and Reverse Holo versions of a card? Easy.

# Request multiple print types in a single call
curl "https://api.justtcg.com/v1/cards?tcgplayerId=67890&printing=Normal,Foil,Reverse Holo" \
  -H "x-api-key: YOUR_API_KEY"

One call, one response, all the data you need. That's the JustTCG way.

What Can You Build With This?

This isn't just a minor tweak; it's a feature that unlocks more efficient and powerful applications. Here are a few ideas:

  • Smarter Inventory Views: Build a dashboard for a local game store that shows all "sellable" inventory (e.g., everything near-mint and lightly-played) in one unified view.
  • Comprehensive Collection Trackers: Allow your users to see the value of their entire collection at a glance, instantly fetching prices for both their foil and non-foil cards together.
  • Efficient Arbitrage Tools: Your "Market Scanner" or "Arbitrage Hunter" tools just got a speed boost. Compare prices across multiple conditions from a single source of truth with fewer API calls.

Looking Ahead: Even More Control

This is another step in our journey to build the ultimate TCG pricing API for developers. We're already thinking about what's next. We've heard the requests, and we're exploring how to give you even more granular control. What if you wanted to fetch everything except a specific condition? Adding exclusion filtering is high on our list to give you that ultimate fine-tuning capability.

This update is live right now. Dive into the updated API documentation to see the new parameters in detail.

As always, we're excited to see what you build. If you use this new filtering power in your project, let us know on Twitter/X!

Happy building.

J
Published by

JustTCG Editor

August 6, 2025

Share this article