Estimate position

Estimate the margin that would be required for maintaining the specified position. Margin estimates are scaled to asset decimal places. If the optional collateral available argument is supplied, the response also contains the estimate of the liquidation price. Liquidation price estimates are scaled to asset decimal places by default, unless an argument to scale to market decimal places is specified in the request.

Query Parameters

marketId string required

Market ID to estimate position for.

openVolume int64 required

Open volume. This field is a signed integer scaled to the market's position decimal places. A negative number denotes a short position.

collateralAvailable string

Collateral available for the position. If provided then response will contain the liquidation price estimate. Collateral available needs to be provided scaled to asset decimal places. Liquidation price returned is scaled to asset decimal places by default.

scaleLiquidationPriceToMarketDecimals boolean

Whether the liquidation price estimates should be scaled to market decimal places or by asset decimal places. If not set, asset decimal places are used.

Responses

• 200
• 500
• default

---

A successful response.

application/json

Schema

Example (from schema)

---

Schema

liquidation object

Liquidation price range estimate for the specified position. Only populated if available collateral was specified in the request.

bestCase object

Liquidation price estimate assuming no slippage.

includingBuyOrders string

Liquidation price assuming buy orders start getting filled.

includingSellOrders string

Liquidation price assuming sell orders start getting filled.

openVolumeOnly string

Liquidation price for current open volume ignoring any active orders.

worstCase object

Liquidation price estimate assuming slippage cap is applied.

includingBuyOrders string

Liquidation price assuming buy orders start getting filled.

includingSellOrders string

Liquidation price assuming sell orders start getting filled.

openVolumeOnly string

Liquidation price for current open volume ignoring any active orders.

margin object

Margin level range estimate for the specified position.

bestCase object

Margin level estimate assuming no slippage.

asset string

Asset ID for which the margin levels apply.

collateralReleaseLevel string

Collateral release level value. This field is an unsigned integer scaled to the asset's decimal places.

initialMargin string

Initial margin value. This field is an unsigned integer scaled to the asset's decimal places.

maintenanceMargin string

Maintenance margin value. This field is an unsigned integer scaled to the asset's decimal places.

marketId string

Market ID for which the margin levels apply.

partyId string

Party ID for whom the margin levels apply.

searchLevel string

Margin search level value. This field is an unsigned integer scaled to the asset's decimal places.

timestamp int64

Timestamp in Unix nanoseconds for when the ledger entry was created.

worstCase object

Margin level estimate assuming slippage cap is applied.

asset string

Asset ID for which the margin levels apply.

collateralReleaseLevel string

Collateral release level value. This field is an unsigned integer scaled to the asset's decimal places.

initialMargin string

Initial margin value. This field is an unsigned integer scaled to the asset's decimal places.

maintenanceMargin string

Maintenance margin value. This field is an unsigned integer scaled to the asset's decimal places.

marketId string

Market ID for which the margin levels apply.

partyId string

Party ID for whom the margin levels apply.

searchLevel string

Margin search level value. This field is an unsigned integer scaled to the asset's decimal places.

timestamp int64

Timestamp in Unix nanoseconds for when the ledger entry was created.

{
  "liquidation": {
    "bestCase": {
      "includingBuyOrders": "string",
      "includingSellOrders": "string",
      "openVolumeOnly": "string"
    },
    "worstCase": {
      "includingBuyOrders": "string",
      "includingSellOrders": "string",
      "openVolumeOnly": "string"
    }
  },
  "margin": {
    "bestCase": {
      "asset": "string",
      "collateralReleaseLevel": "string",
      "initialMargin": "string",
      "maintenanceMargin": "string",
      "marketId": "string",
      "partyId": "string",
      "searchLevel": "string",
      "timestamp": "string"
    },
    "worstCase": {
      "asset": "string",
      "collateralReleaseLevel": "string",
      "initialMargin": "string",
      "maintenanceMargin": "string",
      "marketId": "string",
      "partyId": "string",
      "searchLevel": "string",
      "timestamp": "string"
    }
  }
}

An internal server error

application/json

Schema

Example (from schema)

---

Schema

code int32
details object[]
Array [
@type string
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:
• 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.)
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.
]
message string

{
  "code": 0,
  "details": [
    {
      "@type": "string"
    }
  ],
  "message": "string"
}

An unexpected error response.

application/json

Schema

Example (from schema)

---

Schema

code int32
details object[]
Array [
@type string
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:
• 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.)
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.
]
message string

{
  "code": 0,
  "details": [
    {
      "@type": "string"
    }
  ],
  "message": "string"
}

Loading...