Verticals

Every product on Tradepost lives in a vertical — an asset type with its own data shape. All verticals share one structure:

AssetType → Asset → AssetConfiguration → Item

• Asset — the identity: the card, the set, the event, the coin
• AssetConfiguration — a specific tradeable product of that identity: the print variant, the box format, the parking pass. This is what orders and strategies target
• Item — a physical unit: its condition, grade, section/row, quantity

Payloads that carry products — webhook events, offer flows — split into four sections along those lines:

{
  "asset_type": "<ASSET_TYPE>",
  "external_ids": { ... },
  "asset_details": { ... },
  "config_details": { ... },
  "item_details": { ... }
}

external_ids maps platform-specific identifiers (TCGPlayer, SeatGeek, etc.) for matching against your own catalog. The other sections are asset-type-specific — each vertical page below documents its fields.

Supported verticals

Vertical	Identifier	Description
Tickets	TICKET	Event tickets — concerts, sports, theater
Trading Cards	TRADING_CARD	Single cards, graded or raw — Pokémon, Magic, Yu-Gi-Oh and more
Sealed TCG	SEALED_TCG	Sealed trading card game products — booster boxes, packs, cases
Sealed Wax	SEALED_WAX	Sealed sports card products — hobby boxes, packs, cases
Coins	COIN	Collectible coins — US Mint releases, commemoratives, numismatic
Lego	LEGO	Lego sets, minifigures, and gear

Looking up asset type IDs

Most endpoints reference asset types by internal id (UUID), not the string identifier. Look it up once:

query A($i: ListAssetTypesInput!) {
  assetTypes(input: $i) {
    assetTypes { id type slug displayName platformEnabled tpxEnabled }
    pagination { totalCount }
    error { message code }
  }
}

{ "i": { "type": "SEALED_TCG" } }

Field	Type	Description
type	AssetTypeEnum	Filter by identifier (TICKET, SEALED_TCG, …)
tpxEnabled	Boolean	Filter to types available via the partner API
platformEnabled	Boolean	Filter to types enabled on the consumer marketplace
pagination	SimplePaginationInput	{ limit, offset }

Forward compatibility

Accept unknown fields without validation errors. New fields may be added to any payload section at any time; each vertical's field set is otherwise stable.