Skip to main content

Unified card data.
Connected queries.

Organize cards by name, set, number, language and version. Use consistent records across search, listings, inventory and collections.

Search input
query searches by name or set
Catalog output
items contains card records; total is the match count
Business mapping
Card ID and your listing or collection record
Query → Card record03 recordsResponse
Card record

Charizard ex

SV03: Obsidian Flames

Card number
223/197
Print language
English
Card variant
Holofoil
Rarity
Special Illustration Rare
tcgplayer:509980
CardSetPrinting
3 records

Reusable data for every card.

Find the right card and distinguish names, sets and versions.

Find a card. Confirm its identity.

From a name search to a complete record.

Core card details

Organize names, categories, sets, and card numbers into consistent records for search, detail, and entry screens.

Card record linking

Use card IDs to link catalog records so recognition, listings and collections reference the same card data.

Similar art. Distinct versions.

Release details deserve their own fields.

Set & number

Show set and number separately. Use both to verify and choose cards with the same name across sets.

Language & version

Keep language and foil variants distinct so your app can show differences without merging separate releases.

One catalog. Many uses.

Shared card data across your workflows.

Search & detail views

Use returned card data in search, filters and detail views. Select relevant fields and reduce duplicate maintenance across pages.

Connect more data

Query prices or Population using confirmed card records. Keep variant and language filters aligned with the target card.

Keep catalog and business data distinct.

One catalog entry can be referenced by many listings, inventory entries, and collection records.

Catalog card

Keep names, sets, numbers, languages, and variants in a shared record referenced across pages and features.

Your business records

Your system manages quantities, purchase costs, selling prices and collection notes. One catalog card can link to multiple batches or copies.

Linked view

Fetch card details by ID and combine with local fields for listing or collection views. Business records stay independent of catalog updates.

Find the record. Connect your business.

Keep card details consistent from search to confirmation and linking.

01

Submit search criteria

Search by card name or known set, using details already in your business.

02

Verify the target record

Show set, number, language and version so users can confirm the exact card.

03

Save card links

Link card IDs to listings, inventory or collections. Maintain catalog data separately from your business fields.

Try in Playground

Explore request parameters and responses.

Beyond card names, With details that distinguish each card.

Show names alongside set, number, version and language so similar records stay distinct in search and details.

Search input
query searches by name or set
Catalog output
items contains card records; total is the match count
Business mapping
Card ID and your listing or collection record
View Catalog API docs
GET /example/catalog
RequestResponse
{
  "sample": true,
  "total": 1,
  "items": [
    {
      "card_id": "tcgplayer:509980",
      "name": "Charizard ex",
      "game": "Pokémon",
      "set": "SV03: Obsidian Flames",
      "card_number": "223/197",
      "language": "en",
      "variant": "Holofoil",
      "rarity": "Special Illustration Rare"
    }
  ]
}

One card identity, across every use.

One catalog for search, entry, and display.

01

Product catalog

Confirm catalog entries when listing to keep names, sets, and variants consistent across matching products.

Explore solution
02

Standardize inventory

Link incoming batches to catalog cards. After review, differently named entries can point to the same record.

Explore solution
03

Collection search

Search by name, confirm set, language and version, then save to a personal collection with notes.

Explore solution

Before you integrate.

More questions? Contact us

How do I distinguish cards with the same name or art?

Use set, number, language and version to confirm a record. Name or image alone cannot capture every release difference; keep these fields visible in search.

How does a catalog differ from inventory management?

The catalog provides shared card details. Your inventory tracks physical quantities, locations, costs and movement. Link both to reuse card data while keeping your business rules.

How should multiple matches be displayed?

List candidates with set, number, language and version for review. Do not merge records by name alone.

Does catalog coverage guarantee price and Population data?

Not always. Catalog, recognition, price, and Population coverage differ. Show unavailable data as missing, never as a zero price or count.

How do I link existing listings and inventory?

Match candidate records using existing names, sets, and numbers. Save card ID links after confirmation, keeping original business IDs and history.

Can I get catalog data in bulk?

Yes. Define scope by category, set, language, and fields, then agree on delivery format and update frequency. Discuss your data needs

Tell us about
card business.

Connect an API, request a key or discuss your data needs.
Tell us what you are building. Let us find the next step.

  • Start with your use case

    Define product goals, data scope, and API needs.

  • Find the right integration

    Combine recognition, imaging and data.

  • Discuss trial access

    Once the plan is agreed, we help you get an API key.

Services of interestSelect any

By submitting, you agree we may contact you about this inquiry.

Request submission is not connected in this preview.

One card. Your first API call.

Try preset requests and responses in Playground, or contact us for an API key.