List positions
GET/api/v2/positions
Get a list of all of a party's positions
Request
Query Parameters
Restrict positions to those related to the given parties.
Restrict positions to those on the given markets.
Whether to return all derived parties from AMMs for the given party.
Number of records to be returned that sort greater than row identified by cursor supplied in 'after'.
If paging forwards, the cursor string for the last row of the previous page.
Number of records to be returned that sort less than row identified by cursor supplied in 'before'.
If paging forwards, the cursor string for the first row of the previous page.
Whether to order the results with the newest records first. If not set, the default value is true.
Responses
- 200
- 500
- default
A successful response.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- ]
positions object
Page of positions data and corresponding page information.
edges object[]
Page of positions data and their corresponding cursors.
Cursor that can be used to fetch further pages.
node object
Position data for a party on a market.
Average entry price for the position, the price is an integer, for example 123456
is a correctly
formatted price of 1.23456
assuming market configured to 5 decimal places.
Total fees paid by a party on a market (liquidity, infrastructure, treasury, buy-back, high volume maker fee).
Fees paid since opening the current position.
Total funding payment amounts received or paid by a party on a market.
Funding payments received or paid since opening the current position.
Sum of profit that could not be paid due to loss socialisation.
Total maker fees received by a party on a market.
Maker fees received since opening the current position.
Market ID in which the position is held.
Open volume for the position, value is signed +ve for long and -ve for short.
Party ID holding the position.
Possible values: [POSITION_STATUS_UNSPECIFIED
, POSITION_STATUS_ORDERS_CLOSED
, POSITION_STATUS_CLOSED_OUT
, POSITION_STATUS_DISTRESSED
]
Default value: POSITION_STATUS_UNSPECIFIED
Position status, indicating whether the party was distressed and had orders cancelled or was closed out.
Realised profit and loss for the position, value is signed +ve for long and -ve for short. This field is a signed integer scaled to the market's decimal places.
Total taker fees paid by a party on a market.
Taker fees paid by party on a market since opening their current position. The current position is counted whenever the party changed sides (long <=> short), or a position was opened.
Unrealised profit and loss for the position, value is signed +ve for long and -ve for short. This field is a signed integer scaled to the market's decimal places.
Timestamp for the latest time the position was updated.
pageInfo object
Page information that is used for fetching further pages.
End cursor.
Indicator if there is a next page.
Indicator if there is a previous page.
Start cursor.
{
"positions": {
"edges": [
{
"cursor": "string",
"node": {
"averageEntryPrice": "string",
"feesPaid": "string",
"feesPaidSince": "string",
"fundingPaymentAmount": "string",
"fundingPaymentAmountSince": "string",
"lossSocialisationAmount": "string",
"makerFeesReceived": "string",
"makerFeesReceivedSince": "string",
"marketId": "string",
"openVolume": "string",
"partyId": "string",
"positionStatus": "POSITION_STATUS_UNSPECIFIED",
"realisedPnl": "string",
"takerFeesPaid": "string",
"takerFeesPaidSince": "string",
"unrealisedPnl": "string",
"updatedAt": "string"
}
}
],
"pageInfo": {
"endCursor": "string",
"hasNextPage": true,
"hasPreviousPage": true,
"startCursor": "string"
}
}
}
An internal server error
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- If no scheme is provided,
https
is assumed. - An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
- Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
- ]
details object[]
A URL/resource name that uniquely identifies the type of the serialized
protocol buffer message. This string must contain at least
one "/" character. The last segment of the URL's path must represent
the fully qualified name of the type (as in
path/google.protobuf.Duration
). The name should be in a canonical form
(e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they
expect it to use in the context of Any. However, for URLs which use the
scheme http
, https
, or no scheme, one can optionally set up a type
server that maps type URLs to message definitions as follows:
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com.
Schemes other than http
, https
(or the empty scheme) might be
used with implementation specific semantics.
{
"code": 0,
"details": [
{
"@type": "string"
}
],
"message": "string"
}
An unexpected error response.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- If no scheme is provided,
https
is assumed. - An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
- Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
- ]
details object[]
A URL/resource name that uniquely identifies the type of the serialized
protocol buffer message. This string must contain at least
one "/" character. The last segment of the URL's path must represent
the fully qualified name of the type (as in
path/google.protobuf.Duration
). The name should be in a canonical form
(e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they
expect it to use in the context of Any. However, for URLs which use the
scheme http
, https
, or no scheme, one can optionally set up a type
server that maps type URLs to message definitions as follows:
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com.
Schemes other than http
, https
(or the empty scheme) might be
used with implementation specific semantics.
{
"code": 0,
"details": [
{
"@type": "string"
}
],
"message": "string"
}