Conditional Bid
A standing buy order defined by a set of conditions. When an item is submitted that matches those conditions, the bid is eligible to fill.
Condition types
Bids are placed against identifiers and attributes — not a single asset. Examples:
| Condition type | Example |
|---|---|
| Event ID + seat location | event_id: 12345 + section: 118 + row: 1-10 |
| TCGPlayer Product ID | TCGPLAYER: 593355 + condition: UNOPENED |
| SKU | sku: ABC-123 |
| UPC | upc: 012345678901 |
One bid with broad conditions (e.g., "Event ID X, any lower bowl section, rows 1–10") can match hundreds of potential items.
Constraints
Conditional Bids support additional constraints:
- Price ceiling (max per unit)
- Quantity cap (total units to fill)
- Min quantity per checkout (minimum units per transaction)
- Checkout exchanges (which platforms can execute — e.g., Tradepost, StubHub, etc.)
- Time window (bid expiration)
Lifecycle
Bids move through these states: NOT_FILLED → PARTIALLY_FILLED → FILLED, or can be CANCELLED, EXPIRED, ON_HOLD (risk review), or DELETED (soft-deleted, permanently removed by cleanup job after retention period).
Why it matters
- Demand is pre-staged, enables instant cash offers in under 5ms to sellers
- One bid has many potential fills, so you can programmatically source at scale
- Bids compete in the background — no public auction mechanics, markets are largely dark
info
For full schema details and API integration, see the Conditional Bidding API Reference.