Skip to main content
GET
Wallet combo redemptions and reductions
Returns the canonical combo redemption and reduction history for one wallet. This is the wallet-scoped form of GET /v3/combos/redemptions. In plain language, each row tells you whether the wallet redeemed its entire combo or removed settled legs and kept a smaller combo. The compact fields answer how many legs changed; the leg arrays and position IDs provide the exact market and on-chain details for follow-up queries. Unlike a basic combo activity row, the response makes the before-and-after transition explicit. See How this differs from Polymarket combo activity for the consumer and developer comparison.

Request

Query parameters

Example

Choosing this endpoint

  • Use redemption_scope=full for terminal whole-combo redemptions.
  • Use redemption_scope=partial for post-resolution compression into a smaller combo, including a three-leg combo becoming a two-leg combo when Polymarket emits that transition.
  • Use event_kind=Extracted for structural full/reduced/residual lineage. Extraction is marked as a reduction, but not as a redemption.
  • Use the default all when reconstructing the wallet’s complete combo redemption and transformation history.
  • Use the global endpoint when the wallet is unknown or when correlating one condition, position, or transaction across wallets.
  • Read source_leg_count, removed_leg_count, remaining_leg_count, and leg_transition when you only need to know what changed in that redemption.
  • Read market_token_id, leg_result, leg_current_price, and leg_price_source on each leg when you need an actionable standard-market identifier and outcome state.
  • Read remaining_combo to see the resulting combo position and whether the wallet still holds a positive balance. Use the combo positions endpoint for full position, cost, and P&L context.
For a consumer-facing summary, display redemption_scope and leg_transition first. For a developer workflow, use the source and destination IDs as stable joins, then use market_token_id from each changed leg with price, order-book, trade, or candle endpoints. Existing standard and combo position endpoints are unchanged.

Authorizations

x-api-key
string
header
required

Path Parameters

address
string
required

Wallet address

Pattern: ^0x[a-fA-F0-9]{40}$

Query Parameters

market_id
string

One or more comma-separated combo condition IDs. Matches any condition in the lineage.

condition_id
string

Combo condition ID. Matches any condition in the lineage.

Pattern: ^0x[a-fA-F0-9]{62}$
position_id
string

Primary, source, destination, or underlying position ID

Pattern: ^[0-9]+$
event_kind
enum<string>
Available options:
PositionRedeemed,
Compressed,
ConvertedOnEvent,
ConvertedToYesBasket,
Extracted,
Injected,
MergedFromYesBasket,
MergedOnCondition,
MergedOnEvent,
SplitOnCondition,
SplitOnEvent,
Unwrapped,
Wrapped,
all
redemption_scope
enum<string>
default:all

full = terminal redemption; partial = non-terminal post-resolution compression; transformation = non-redemption lifecycle lineage

Available options:
full,
partial,
transformation,
all
redemption_type
enum<string>
default:all
Available options:
FULL_COMBO,
PARTIAL_COMBO,
COMBO_TRANSFORMATION,
all
tx_hash
string

Exact Polygon transaction hash

Pattern: ^0x[a-fA-F0-9]{64}$
after
integer<int64>

Inclusive Unix timestamp in seconds

Required range: x >= 0
before
integer<int64>

Inclusive Unix timestamp in seconds

Required range: x >= 0
limit
integer
default:100
Required range: 1 <= x <= 300
offset
integer
default:0
Required range: x >= 0

Response

Wallet combo redemptions and reductions

address
string
redemptions
object[]
rows_returned
integer
has_more
boolean
offset
integer
limit
integer
position_type
string
Allowed value: "combo"
source
string
Allowed value: "v3.wallet_combos.redemptions"