Our #1 pick · Multi-game app infrastructure. Recognition has its own billing. Catalog credits are not a scan allowance.
Published API overview
| Option | What to evaluate | Decision detail |
|---|---|---|
| Game coverage | 9 games | Check current set and language coverage with the provider. |
| API access | REST + GraphQL | EU + US pricing |
| Published entry plan | $19 / mo | 25,000 data credits |
Is TCGGraph right for your app?
Start with the game coverage and data fields your interface needs. Then check source timestamps, printing identity and usage limits against a representative sample of your own cards. The published entry plan alone does not establish the best cost for a production workload.
This profile summarizes public documentation. It does not represent an independent performance test or an endorsement from TCGGraph.
Where TCGGraph fits in a production card app
The service is our preferred option when one application needs several games, regional price references and a path into recognition. Its current game list includes Pokémon, Magic, Yu-Gi-Oh!, One Piece, Lorcana, Star Wars: Unlimited, Digimon, Grand Archive and Dragon Ball Super. Test required sets and printings within those games before making a completeness assumption.
REST and GraphQL are alternative ways to query the catalog. A simple lookup may be clearest through REST, while a screen with selected fields can benefit from GraphQL. Choose around the response your app needs and inspect the cost of each underlying operation.
Understand catalog credits, scans and updates
Catalog reads and card recognition have separate metering. A plan’s data allowance should not be described as a scan allowance. Estimate history requests, searches and lookups independently, then add recognition only if users will actually scan cards.
The documentation also describes signed webhook events and price watches. These can support catalog updates and user-requested alerts, but the receiver still needs signature checks, duplicate handling and reconciliation after an outage.
A practical first integration
Start by searching a representative printing in the explorer, checking its market and finish fields, and saving a holding in your own database. Then run a price refresh that leaves ownership information intact. Repeat with missing quotes and a corrected printing so the integration covers the cases a real collection will encounter.
For a step-by-step path, use the TCGGraph integration guide. For a buying decision, compare the multi-game architecture and workload pricing guides.
Frequently asked questions
How many games does TCGGraph support?
The current catalog and GraphQL reference list nine games. Some older marketing copy still refers to eight; use the current game list and test the individual printings you require.
Does TCGGraph offer annual billing?
Its current pricing page includes monthly and yearly options. Check the selected period, total charge and allowance reset behavior before purchase.
Is this an independent TCGGraph review?
No. TCG API Guide and TCGGraph share ownership. The recommendation reflects the stated multi-game app brief and public documentation, not an independent benchmark.