Asset Types
Overview
TPX supports multiple asset types, each with specific data requirements and formats. Every asset type follows a standardized structure with four main components:
- External IDs - Platform-specific identifiers for cross-platform matching
- Asset Details - Asset-level information (applies to all items of this asset)
- Config Details - Configuration-level information (asset grouping and categorization)
- Item Details - Item-specific information (condition, quantity, location, etc.)
Supported Asset Types
| Asset Type | Identifier | Description | Status |
|---|---|---|---|
| Ticket | TICKET | Event tickets (concerts, sports, theater) | Active |
| Sealed TCG | SEALED_TCG | Sealed trading card game products (booster boxes, packs, etc.) | Active |
| Sealed Wax | SEALED_WAX | Sealed sports card wax products (hobby boxes, packs, cases) | Active |
| Coin | COIN | Collectible coins (US Mint releases, commemoratives, numismatic) | Active |
| Lego | LEGO | Lego sets, minifigures, and gear | Active |
| Trading Card | TRADING_CARD | Single trading cards (Pokemon, Magic, Yu-Gi-Oh, etc.) — graded or raw | Active |
List Asset Types
Most endpoints across TPX (including Advanced Strategies) reference asset types by their internal id (UUID), not the string identifier above. Use this query to look up the id for an asset type.
query AssetTypes($input: ListAssetTypesInput!) {
assetTypes(input: $input) {
assetTypes {
id
type
slug
displayName
platformEnabled
tpxEnabled
}
pagination {
totalCount
}
error { message code }
}
}
Input Fields
| Field | Type | Required | Description |
|---|---|---|---|
| type | AssetTypeEnum | No | Filter by a single identifier (TICKET, SEALED_TCG, etc.) |
| platformEnabled | Boolean | No | Filter to types enabled on the consumer marketplace |
| tpxEnabled | Boolean | No | Filter to types available via TPX (partner API) |
| includeMedia | Boolean | No | Include media URLs (default false) |
| pagination | SimplePaginationInput | No | { limit, offset } — defaults to limit: 20, offset: 0 |
Filter to a Single Asset Type
{
"query": "query AssetTypes($input: ListAssetTypesInput!) { assetTypes(input: $input) { assetTypes { id type slug } error { message code } } }",
"variables": {
"input": { "type": "SEALED_TCG" }
}
}
List All TPX-enabled Asset Types
{
"query": "query AssetTypes($input: ListAssetTypesInput!) { assetTypes(input: $input) { assetTypes { id type displayName } } }",
"variables": {
"input": { "tpxEnabled": true }
}
}
Authentication
This query is open — it can be called with or without auth. Partner integrations typically include their API key for consistency.
Data Structure
All asset types follow this structure in webhook messages:
{
"asset_type": "<ASSET_TYPE>",
"external_ids": { ... },
"asset_details": { ... },
"config_details": { ... },
"item_details": { ... }
}
See each asset type page for detailed field specifications and examples.
Forward Compatibility
Your integration should accept unknown fields without validation errors. New fields may be added to any payload section at any time.