Skip to main content
GET
Wallet combo summary
Returns a combo-only summary for a wallet. Use this endpoint when you want to inspect combo exposure separately from the standard wallet summary. For an all-in wallet summary, call GET /v3/wallets/{address}?include_combos=true.
Owner addresses. Pass an owner EOA as the wallet address and the response combines the EOA’s Polymarket wallets (Safe, proxy, deposit wallets) that have data for this endpoint. Passing a Safe, proxy or deposit wallet returns just that wallet, as before. Combined responses list the combined wallets in wallets. See Owner addresses.

Request

Path parameters

Query parameters

All optional. They scope only the win and loss counts; see Time windows.

Example

Past 7 days

Response fields

With a window, the response also has these top-level fields:

Win and loss counts

A combo position is won or lost once its legs resolve: a YES position wins when every leg wins and loses as soon as any leg loses; a NO position is the reverse. The counts cover every combo position the wallet has held, all time, whether or not it was redeemed, including positions it sold or transferred before the combo resolved. Open positions are not counted. To list the positions behind the all-time counts, call Wallet Combo Positions with status=resolved_win, status=resolved_loss, or status=resolved (both). That listing is not window-scoped.

Time windows

With period=1d, 7d, 30d, or custom, win_count, loss_count, resolved_count and win_rate count only the combo positions that settled inside the window. P&L, open_combo_count, closed_combo_count, balance_count and last_activity_at are always all time.
  • A combo settles at its first payout to any holder. Both sides of a combo share that time, so a lost position is placed when the winning side was paid.
  • A small share of resolved combos has no recorded payout. Their positions count in the all-time totals but in no window, until a payout is recorded. Most of them are losses, so a windowed win_rate can read slightly high.
  • The window is half-open: after is inclusive and before is exclusive, like the Combo P&L Leaderboard. Wallet Combo Redemptions treats before as inclusive.
  • An invalid window returns 400 invalid_request, for example period=1y, period=custom with no bound, after not less than before, or window=7d (use period). Windowed counts can briefly return 503 combo_window_unavailable when the payout data is catching up; retry, or call without a window for the all-time counts.

Owner address fields

Present only when you pass an owner EOA. See Owner addresses. Counts and P&L are summed across the combined wallets, win_rate is recomputed from the summed counts, and last_activity_at is the latest of them. With a window, every combined wallet uses the same window.

Authorizations

x-api-key
string
header
required

Path Parameters

address
string
required

Wallet address, or an owner EOA to combine every Polymarket wallet it owns

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

Query Parameters

period
enum<string>
default:all

Window for the win/loss counts. All Time is the default. Custom requires after or before. Fixed periods and All Time forbid explicit bounds.

Available options:
all,
1d,
7d,
30d,
custom
after
integer<int64>

Inclusive custom lower bound in Unix seconds. Accepted only with period=custom (or no period).

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

Exclusive custom upper bound in Unix seconds. Accepted only with period=custom (or no period).

Required range: 0 <= x <= 9999999999

Response

Wallet combo summary

address
string
summary
object | null
rows_returned
integer
position_type
string
source
string
elapsed_ms
integer
period
string

Present only with a window: 1d, 7d, 30d, or custom

window
object

Present only with a window: the bounds the counts used, after inclusive and before exclusive

wallets
object[]

Present only for an owner EOA: the combined wallets