Vinter API
Search
⌃K

Active Multi Assets

The active multi assets endpoint returns information on all multi assets.
The endpoint returns the index symbols that you can use when you query other endpoints. The endpoint does not require an API key and does not accept any parameters. The endpoint also returns the rebalance weights as of the last review date. The rebalance weights are updated after the official end-of-day value and before 00:00 UTC the day of rebalance Example URL
This endpoint returns information for the current multi assets indexes. Below is a list of the current fields that the endpoint provide

Response Fields

Field
Type
Description
symbol
string
The index symbol
weights
object
Current Index constituents and rebalance weights
previous_rebalance_date
string
Date representing the previous rebalance date
next_rebalance_date
string
Date representing the next rebalance date
previous_review_date
string
Date representing the previous review date
next_review_date
string
Date representing the next review date
next_rebalance_weights
object
Upcoming index constituents and rebalance weights
indicative_rebalance_weights
object
These weights give an indication of the upcoming rebalance weights.
indicative_rebalance_date
string
Date representing the Indicative rebalance weights calculation date
short_name
string
The index symbol short name
long_name
string
The index symbol long name
get
https://www.vinterapi.com/api/v3/active_multi_assets/

Endpoint Updates At Rebalancing

The endpoint gets continuously updated between the calculation date and the rebalancing date for each index
  1. 1.
    One day after the calculation date the next_rebalance_weights field is updated with the new rebalance weights for the index.
  2. 2.
    After the publication time at the day of rebalancing the next_rebalance_weights field is moved to the weights field. After moving the next_rebalance_weights field to the weights field, the following fields are set to Null.
    1. 1.
      next_rebalance_date
    2. 2.
      next_rebalance_weights
    3. 3.
      next_review_date
    4. 4.
      previous_review_date
    5. 5.
      previous_rebalance_date
    6. 6.
      indicative_rebalance_weights
    7. 7.
      indicative_rebalance_date
The fact that these fields are null only if the weights field contain the rebalancing weight for the next coming rebalance period it becomes easy to verify which rebalancing values to use. Vinter suggests however that you retrieve the new rebalancing weights a couple of days before rebalancing. This is always possible since review date and rebalance date are never the same.
Previous
Multi Assets Indexes
Next
Multi Assets Daily
Last modified 11d ago