Get vesting balance statistics

GET 
https://api.n00.testnet.vega.rocks/api/v2/party/vesting/stats/:partyId

Get information about a party's vesting rewards

Request

Path Parameters

partyId stringrequired

Party ID to query the vesting stats for.

Responses

200

A successful response.

application/json

Schema

Schema

epochSeq uint64

Epoch for which this information is valid.

partyId string

Party ID.

quantumBalance string

The balance of the party, in quantum.

rewardBonusMultiplier string

Reward bonus multiplier.

summedQuantumBalance string

The balance of the party and derived keys, in quantum.

summedRewardBonusMultiplier string

Bonus multiplier applied on the reward, summed across all derived accounts.

Example (from schema)

{
  "epochSeq": "string",
  "partyId": "string",
  "quantumBalance": "string",
  "rewardBonusMultiplier": "string",
  "summedQuantumBalance": "string",
  "summedRewardBonusMultiplier": "string"
}

500

An internal server error

application/json

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

Example (from schema)

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

default

An unexpected error response.

application/json

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

Example (from schema)

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

• curl
• python
• go
• nodejs

• CURL

curl -L -X GET 'https://api.n00.testnet.vega.rocks/api/v2/party/vesting/stats/:partyId' \
-H 'Accept: application/json'

Request Collapse all

Base URL

https://api.n00.testnet.vega.rocks

Parameters

partyId — pathrequired

ResponseClear

Click the Send API Request button above and see the response here!