Understanding Set Types

Learn how to classify and work with different types of trading card sets, including the distinction between parallel sets and variation sets.

What are Set Types?

Trading card sets come in many forms beyond the standard base set. Understanding the different set types helps you accurately categorize and manage your card data. The Trading Card API provides boolean flags and relationships to help you distinguish between these types.

Set Type Overview

Base Sets

The primary set of cards in a product release. Base sets contain the core cards that define the product.

Characteristics:

Main checklist of the product
Usually the largest set in a product
Other sets reference the base set as their parent

Example: The 350-card base set in 2025 Topps Allen & Ginter

Parallel Sets

Complete reproductions of a base set with a different visual treatment. Parallels include every card from the base set.

Characteristics:

Same card numbers as the base set
Same number of cards as the base set
Different card stock, finish, or numbering (e.g., Gold /50, Refractor)
is_parallel: true in the API

Example: 2025 Topps Chrome Refractor parallel - all 350 base cards available as Refractors

Variation Sets

Partial reproductions of a base set with a different visual treatment. Variations include only a subset of the base cards.

Characteristics:

Same card numbers as the base set (but fewer cards)
Different visual treatment or design
Typically more limited in scope
is_variation: true in the API

Examples:

2025 Topps Allen & Ginter "Tin Type Variations" - Only 99 of 350 cards available in vintage tin-type style
2025 Topps Allen & Ginter "Chrome Variations" - Only 99 cards available with chrome/refractor finish

Insert Sets

Special themed cards inserted into packs, separate from the base set.

Characteristics:

Different card numbering than base set (usually prefixed, e.g., "INS-1")
Themed content (e.g., "League Leaders", "Rookie Stars")
Variable rarity across the insert set

Autograph Sets

Cards featuring authentic player signatures.

Characteristics:

May be standalone or parallel versions of other sets
Usually serial numbered
Higher value and collectibility

Relic Sets

Cards containing pieces of game-used memorabilia (jerseys, bats, etc.).

Characteristics:

Physical memorabilia embedded in the card
May be standalone or combined with autographs
Usually serial numbered

Parallel vs Variation: Key Differences

Aspect	Parallel (`is_parallel: true`)	Variation (`is_variation: true`)
Card Count	Same as base set	Subset of base set
Card Numbers	All base card numbers	Only some base card numbers
Completeness	Complete parallel of base	Partial variation of base
Example	Gold /50 (all 350 cards)	Tin Type (99 of 350 cards)

When to Use Each

Use is_parallel: true when:

The set includes every card from the base set
Collectors can build a complete parallel set
The only difference is the card treatment/numbering

Use is_variation: true when:

The set includes only some cards from the base set
The variation applies to a limited selection of players/cards
Collectors cannot complete a full parallel

API Examples

Creating a Variation Set

POST /v1/sets

{
  "data": {
    "type": "sets",
    "attributes": {
      "name": "Tin Type Variations",
      "is_variation": true,
      "card_count": 99
    },
    "relationships": {
      "parent": {
        "data": { "type": "sets", "id": "<base-set-uuid>" }
      },
      "product": {
        "data": { "type": "products", "id": "<product-uuid>" }
      }
    }
  }
}

Creating a Parallel Set

POST /v1/sets

{
  "data": {
    "type": "sets",
    "attributes": {
      "name": "Gold /50",
      "is_parallel": true,
      "card_count": 350
    },
    "relationships": {
      "parent": {
        "data": { "type": "sets", "id": "<base-set-uuid>" }
      },
      "product": {
        "data": { "type": "products", "id": "<product-uuid>" }
      }
    }
  }
}

Response with Set Type Fields

{
  "data": {
    "type": "sets",
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "attributes": {
      "name": "Tin Type Variations",
      "description": "Vintage-style tin type treatment of select base cards",
      "card_count": 99,
      "is_variation": true,
      "is_parallel": false,
      "created_at": "2025-01-15T10:30:00Z",
      "updated_at": "2025-01-15T10:30:00Z"
    },
    "relationships": {
      "parent": {
        "data": { "type": "sets", "id": "base-set-uuid" }
      }
    }
  }
}

Finding Sets by Type

There is no query parameter for the set-type flags. /v1/sets accepts filter[status] and nothing else bracketed, so filter[is_parallel]=true is not a valid parameter — and because unrecognised parameters are silently ignored rather than rejected, sending one returns a full unfiltered page that looks like a valid answer. See Querying Conventions.

Instead, fetch a base set's children with parent_id and read the flags off the rows you get back:

# List every child of a base set: parallels, variations, inserts, autographs
GET /v1/sets?parent_id=BASE_SET_UUID&per_page=100

Then filter client-side on is_parallel, is_variation, is_insert and is_autograph.

Real-World Example: 2025 Topps Allen & Ginter

Here's how a complete product might be structured:

Set Name	Type	is_parallel	is_variation	card_count
Base Set	Base	false	false	350
Gold Border /50	Parallel	true	false	350
Mini	Parallel	true	false	350
Tin Type Variations	Variation	false	true	99
Chrome Variations	Variation	false	true	99
World's Champions	Insert	false	false	50

Reading Set Types: Child Sets vs a Card's Children

If you are consuming the API rather than authoring data, one distinction matters more than everything else on this page.

A parallel, insert, variation or autograph subset is its own set row. Its parent_id points at the base set, and its is_parallel / is_insert / is_variation / is_autograph flags say what kind of release it is. Sibling child sets under one base set are what collectors mean by a rainbow.

A card's children is a different relationship. It holds variations of that one specific card — a photo variation or short print of card #1, say. It does not contain the parallel versions of card #1 from the other child sets.

So: building a rainbow means walking child sets, not expanding a card. Fetching a card with include=children and finding only one or two rows where a rainbow should have a dozen is the symptom of taking the card route.

2024 Prizm Baseball            (root set — parent_id is null)
├── Silver Prizm               (is_parallel)
├── Gold Prizm /10             (is_parallel)
└── Signatures                 (is_autograph)

Card #1's rainbow is card #1 pulled from each child set, joined on card number.

One further consequence of this model: the default /v1/sets listing returns root sets only — those with a null parent_id. Every set on this page other than a base set is therefore absent from that listing until you walk into it with parent_id. That is why the catalog can look far thinner from the outside than it is.

For the full walkthrough — finding the base set, enumerating children, and joining each child's checklist — see Build a Rainbow.

Best Practices

1. Use Parent Relationships

Always link parallels and variations to their parent base set:

"relationships": {
  "parent": {
    "data": { "type": "sets", "id": "<base-set-uuid>" }
  }
}

This enables:

Navigating from variations to base cards
Understanding set hierarchy
Calculating collection completion

2. Be Accurate with Card Counts

Set card_count accurately:

For parallels: Should match the base set count
For variations: Should reflect the actual subset count

3. Document Visual Differences

Use the description field to explain what makes this set different:

{
  "description": "Vintage tin-type photographic treatment on thick cardstock"
}

4. Consider Both Flags

A set can have neither flag (base set, insert), one flag (parallel or variation), but typically not both. If a set reproduces all cards with a treatment, it's a parallel. If it reproduces only some cards, it's a variation.

Common Misconceptions

"Short Print Variations"

Short print variations within a base set (where some base cards have rare photo variations) are different from variation sets. SP variations are typically tracked at the card level, not the set level.

"All Non-Base Sets are Parallels"

Insert sets are neither parallels nor variations - they have their own independent numbering and content.

Next Steps

Build a Rainbow - Walk a base set's parallels end to end
Querying Conventions - Query parameters per resource, partial matching, and root-only listings
Data Models - Complete Set model reference
API Reference - Sets endpoint documentation
Data Provenance - Track where your set data comes from
Building Card Tracker - Build an app using set data

What are Set Types?​

Set Type Overview​

Base Sets​

Parallel Sets​

Variation Sets​

Insert Sets​

Autograph Sets​

Relic Sets​

Parallel vs Variation: Key Differences​

When to Use Each​

API Examples​

Creating a Variation Set​

Creating a Parallel Set​

Response with Set Type Fields​

Finding Sets by Type​

Real-World Example: 2025 Topps Allen & Ginter​

Reading Set Types: Child Sets vs a Card's Children​

Best Practices​

1. Use Parent Relationships​

2. Be Accurate with Card Counts​

3. Document Visual Differences​

4. Consider Both Flags​

Common Misconceptions​

"Short Print Variations"​

"All Non-Base Sets are Parallels"​

Next Steps​

What are Set Types?

Set Type Overview

Base Sets

Parallel Sets

Variation Sets

Insert Sets

Autograph Sets

Relic Sets

Parallel vs Variation: Key Differences

When to Use Each

API Examples

Creating a Variation Set

Creating a Parallel Set

Response with Set Type Fields

Finding Sets by Type

Real-World Example: 2025 Topps Allen & Ginter

Reading Set Types: Child Sets vs a Card's Children

Best Practices

1. Use Parent Relationships

2. Be Accurate with Card Counts

3. Document Visual Differences

4. Consider Both Flags

Common Misconceptions

"Short Print Variations"

"All Non-Base Sets are Parallels"

Next Steps