include_combos=true on supported wallet endpoints when you want the wallet-level response to include both standard market data and combo data.
Base URL
Dedicated combo endpoints
Additive wallet support
These wallet endpoints supportinclude_combos=true:
If a wallet has no combo exposure,
include_combos=true still returns 200 with the normal wallet response and a zero combo contribution or empty combo branch. Clients do not need to know ahead of time whether a wallet has traded combos.
Identifier notes
P&L semantics
Combo P&L uses the same high-level model as standard Polymarket positions: weighted-average cost basis, realized P&L from closes/redeems/merges, and unrealized P&L for open balances when a current price is available. When a combo is redeemed, PolyNode settles the redeemed size against weighted-average entry basis. Fully redeemed winners returnRESOLVED_WIN with zero open entry cost and realized P&L from the redemption payout; fully redeemed losers return RESOLVED_LOSS. Combo redemption activity is normalized to Polymarket’s public PositionRedeemed shape even when the on-chain path used the router or auto-redeemer.
The dedicated redemption endpoints distinguish a terminal redemption, a post-resolution compression into a smaller combo, and a structural extraction. Compressed provides the old/new position transition; Extracted provides full/reduced/residual condition lineage without falsely claiming a payout. Both can show that a three-leg combo became a two-leg combo and return remaining/removed leg sets. See Combo Redemptions.
All aggregate P&L fields are returned as decimal USD numbers. Event-level combo amount fields use decimal strings such as "0.050750" for exact USDC-style display.