Positioning

Aggregate positioning for one instrument across all tracked accounts, over time: total long size, total short size, and the net. Answers ‘is the crowd long or short, and how is that shifting’ — impossible from Polymarket’s per-account API.

GET /v3/perps/positioning/{instrument}

Positioning over time

cURL

curl --request GET \
  --url https://api.polynode.dev/v3/perps/positioning/{instrument} \
  --header 'x-api-key: <api-key>'

200

{
  "data": [
    {
      "as_of": 1783736981912,
      "long_size": "64.73273376",
      "net_size": "0.00196",
      "positions": 159,
      "short_size": "64.73077376"
    },
    {
      "as_of": 1783735057291,
      "long_size": "65.41269",
      "net_size": "0.92601",
      "positions": 160,
      "short_size": "64.48668"
    }
  ],
  "instrument_id": 6,
  "symbol": "BTC-USD"
}

How the whole market is positioned on one instrument, over time. Each row is a point in time with the total long size, total short size, and the net across every tracked account. Watch the net flip, or watch one side build up ahead of a move.

Add after / before (Unix seconds or milliseconds) to bound the window, and limit for the number of points.

This is a cross-account aggregate. Polymarket’s API only exposes one account at a time and keeps no history, so this view doesn’t exist there at all.

Authorizations

x-api-key · string · header · required

Path Parameters

instrument · string · required

Instrument id (6), symbol (BTC-USD), or bare asset (btc).

Query Parameters

after · integer

Window start (Unix s or ms)

before · integer

Window end

limit · integer

Max snapshots (default 500)

Response

200 - application/json

Success