Combo Activity

​

Request

GET /v3/combos/activity

​

Query parameters

​

Example

curl "https://api.polynode.dev/v3/combos/activity?condition_id=0x03d98f6ac4c108c5ca66f79f34908a1d820000000000000000000000000000&limit=10"

{
  "activity": [
    {
      "position_type": "combo",
      "event_kind": "PositionsSplit",
      "wallet_address": "0x63613e3b96f418332d43cd2af8dc321014d15907",
      "combo_condition_id": "0x03d98f6ac4c108c5ca66f79f34908a1d820000000000000000000000000000",
      "amount_usdc": "0.050750",
      "tx_hash": "0xf3a8985f04bf869483ef4163a185f296c834eb827b5e5ae3db5bd44558121d51",
      "block_number": 88276713,
      "timestamp": 1781120055
    }
  ],
  "rows_returned": 10,
  "has_more": true,
  "position_type": "combo",
  "source": "v3.combos.activity"
}

​

Owner address fields

​

Notes

• Use /v3/wallets/{address}/combos/activity when the wallet address is already known.
• Use /v3/combos/redemptions when you need terminal-versus-partial redemption evidence or condition/position lineage.
• Use this endpoint when you are exploring all lifecycle activity for a combo market or position.
• The activity feed is on-chain derived and can include split, merge, redemption, and transfer-related lifecycle rows as those events are observed.
• Public combo redemption rows are normalized to Polymarket’s combo activity shape: router and auto-redeemer redemption paths are returned as event_kind: "PositionRedeemed" with side: "Redeem", a module kind such as Combinatorial, Binary, or NegRisk, and payout_usdc when available.
• When leg metadata is available, resolved combo activity includes leg statuses such as RESOLVED_WIN or RESOLVED_LOSS and leg_current_price values.