Get current volume discount program

Get the current volume discount program for the network. This program may not be active if it has ended and has not been replaced by another.

Responses

• 200
• 500
• default

---

A successful response.

application/json

Schema

Example (from schema)

---

Schema

currentVolumeDiscountProgram object

Volume discount program currently activated on the network.

benefitTiers object[]

Defined benefit tiers ordered by increasing discounts. Determines the level of benefit a party can expect based on performance criteria.

Array [

minimumRunningNotionalTakerVolume string

Required running notional taker volume in quantum units for parties to access this tier.

volumeDiscountFactor string

Proportion of the taker fees to be discounted.

]

endOfProgramTimestamp int64

Timestamp in Unix nanoseconds, after which when the current epoch ends, the program will end and benefits will be disabled.

endedAt int64

Timestamp in Unix nanoseconds, at which the program ended.

id string

Unique ID generated from the proposal that created this program.

version uint64

Incremental version of the program. It is incremented after each program update.

windowLength uint64

Number of epochs over which a volume discount statistics' running volume is evaluated.

{
  "currentVolumeDiscountProgram": {
    "benefitTiers": [
      {
        "minimumRunningNotionalTakerVolume": "string",
        "volumeDiscountFactor": "string"
      }
    ],
    "endOfProgramTimestamp": "string",
    "endedAt": "string",
    "id": "string",
    "version": "string",
    "windowLength": "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"
}

GET /api/v2/volume-discount-programs/current

Request

Base URL

https://vega-data.nodes.guru:3008

curl / cURL

curl -L -X GET 'https://vega-data.nodes.guru:3008/api/v2/volume-discount-programs/current' \
-H 'Accept: application/json'

python / requests

curl -L -X GET 'https://vega-data.nodes.guru:3008/api/v2/volume-discount-programs/current' \
-H 'Accept: application/json'

go / native

curl -L -X GET 'https://vega-data.nodes.guru:3008/api/v2/volume-discount-programs/current' \
-H 'Accept: application/json'

nodejs / axios

curl -L -X GET 'https://vega-data.nodes.guru:3008/api/v2/volume-discount-programs/current' \
-H 'Accept: application/json'