Composition data
What is this endpoint for?
These two endpoints retrieve the constituent-level composition of a Kaiko multi-asset index over time. There are two complementary feeds:
Effective composition (
indices_effective_compo) — the active composition, produced on every index publication.Forecast composition (
indices_forecast_compo) — the composition that takes effect at the next rebalance, projected once per day from the pending review's target weights.
Effective composition
Endpoint
https://us.market-api.kaiko.io/v2/data/index.v1/indices_effective_compoRequest parameters
index_code
Yes
The desired index ticker. Accepts a comma-separated list for multiple indices.
KT10NYC
start_time
Yes
Starting time in ISO 8601 (inclusive). Filters on index_event_ts.
2026-07-22T00:00:00.000Z
end_time
Yes
Ending time in ISO 8601 (exclusive). Filters on index_event_ts.
2026-07-23T00:00:00.000Z
page_size
No
Number of records per page (default 100).
100
continuation_token
No
Token returned in a paged response. Pass it as a query parameter to fetch the next page, and repeat until data is empty.
...
Response Fields
Each element of data is one composition record:
index_code
The ticker of the index
event_ts
The time at which the composition record was produced
last_effective_rebalancing
The time of the rebalance currently in force
index_value
The value for the index publication
divisor
The index divisor
index_event_ts
The time of the index publication the record is derived from
composition.pairs
The list of constituents included in the index
result
Status of the query
Each object in composition.pairs contains:
underlying_instrument
The ticker of the constituent used in the index calculation
base
The base asset of the constituent
quote
The quote asset of the constituent
current_price
The latest price of the constituent
target_weight
The target allocation set at the last rebalance
effective_units
The number of units of the constituent
current_weight
The live allocation of the constituent
underlying_timestamp
The time of the constituent price used
Request example
Response example
Forecast composition
Endpoint
Request parameters
index_code
Yes
The desired index ticker. Accepts a comma-separated list for multiple indices.
KT10NYC
start_time
Yes
Starting time in ISO 8601 (inclusive). Filters on index_event_ts.
2026-07-22T00:00:00.000Z
end_time
Yes
Ending time in ISO 8601 (exclusive). Filters on index_event_ts.
2026-07-23T00:00:00.000Z
page_size
No
Number of records per page (default 100).
100
continuation_token
No
Token returned in a paged response. Pass it as a query parameter to fetch the next page, and repeat until data is empty.
...
Response Fields
Each element of data is one forecast record:
index_code
The ticker of the index
event_ts
The time at which the forecast record was produced
next_forecast_rebalancing
The time at which the forecast basket takes effect
index_value
The value for the index publication
divisor
The index divisor
index_event_ts
The time of the index publication the record is derived from
forecast.pairs
The list of constituents included in the forecast
result
Status of the query
Each object in forecast.pairs contains:
underlying_instrument
The ticker of the constituent used in the index calculation
base
The base asset of the constituent
quote
The quote asset of the constituent
execution_price
The price used to size the forecast units
forecast_weight
The target allocation for the next rebalance
forecast_units
The number of units that will be locked at the next rebalance
underlying_timestamp
The time of the constituent price used
Request example
Response example
Last updated
Was this helpful?
