Smart Money Positioning (Polymarket)
How smart-money wallets are positioned in a single market over the window: net buyers vs. sellers, buy/sell volume split, and volume-weighted entry prices, with a per-wallet breakdown. Pairs with Smart Activity Markets — discover a market there, then drill into it here. Cost-basis PnL/ROI fields are not yet computed and are returned as null.
/v2/polymarket/market/{condition_id}/smart-moneyQuery Parameters
Market condition ID — must match ^0x[0-9a-f]{64}$.
Optional. 1d (default), 7d, 30d, or all_time. Longer windows favor recently-active wallets.
Response Schema
Thresholds defining a smart-money wallet for this response.
Minimum lifetime PnL (USD) to count as smart money.
Minimum per-fill notional (USD) counted.
Rolling window applied (1d, 7d, 30d, all_time).
Market condition ID.
Market title (null if not resolved).
Market slug (null if not resolved).
Distinct smart wallets active in this market in the window.
Smart wallets whose buy volume exceeds sell volume.
Smart wallets whose sell volume exceeds buy volume.
Smart wallets with balanced buy/sell volume.
net_buyers / smart_wallet_count (0–1).
Total smart-money notional (USD).
Buy-side smart notional (USD).
Sell-side smart notional (USD).
Volume-weighted average smart buy price (0–1).
Volume-weighted average smart sell price (0–1).
Realized PnL. Not yet computed — returned as null (see _meta.unavailable_fields).
Total PnL. Not yet computed — returned as null.
Average ROI. Not yet computed — returned as null.
Average win rate. Not yet computed — returned as null.
Top smart wallets in this market by volume (capped).
Smart wallet (Polymarket proxy address).
Wallet lifetime PnL (USD).
This wallet's notional in this market in the window (USD).
buyer, seller, or neutral for this market in the window.
Source, data floor, and field-availability metadata.
Data source identifier.
ISO timestamp; trade data is served from this point onward.
Fields returned as null pending per-wallet cost-basis accounting.
Which fields are exact vs. not yet available.
How smart-wallet coverage relates to the chosen window.
Error Responses
All errors return the same envelope. The code field is stable and programmatically branchable; error and message are human-readable. errors[] is present only on validation failures with field-level detail. See the full error code reference →
Always `false` on error responses.
Short, human-readable title (e.g. 'Invalid API Key.').
Human-readable explanation for the error. Safe to surface in UIs.
Stable, hierarchical machine-readable code (e.g. 'validation.invalid_enum'). Use for programmatic handling.
Link to this code's entry in the Error Reference.
Optional. Present only on validation failures with field-level detail.
Name of the offending parameter.
Field-level machine code.
Human-readable explanation.
Authentication
API Key
To secure your requests, we strongly recommend passing your API key via the X-API-Key header. This prevents sensitive keys from being exposed in access logs or browser history.
X-API-Key: pmx_test_5e8f...Rate Limits
API rate limits are enforced based on the tier associated with your API key. Limits are tracked on two dimensions: requests per second and requests per month. Each completed request counts toward the global monthly quota. Separate endpoint-group monthly limits (matched markets, arbitrage, EV) only advance when the response body has success: true.
Usage is returned on responses via headers such as:
X-RateLimit-Limit-Second: 10X-RateLimit-Remaining-Second: 9X-RateLimit-Limit-Month: 1000X-RateLimit-Remaining-Month: 842Example (endpoint-group, when applicable)X-RateLimit-Limit-Arb-Month: 500X-RateLimit-Remaining-Arb-Month: 412If you exceed a rate limit, the API returns a 429 status with a Retry-After header indicating when you can resume.
Request
Live API Key
Parameters
Response
—Click EXECUTE to send a request →