Index Composition and Input Data

Crypto Index Composition and Input Data

Understand what a crypto index contains and how its value is calculated.

A cryptocurrency index value shows where a benchmark stands. CoinAPI Crypto Index Composition and Input Data helps explain what sits behind that value.

Depending on the index type and available dataset, composition data can be used to inspect index constituents, constituent weights, and historical benchmark structure. Index Input Data provides visibility into the market data and calculation inputs associated with an index definition.

Explore the Docs Get Your API Key

Data Layers

What Sits Behind a Crypto Index?

A crypto index is more than a calculated number. Behind every index value is a methodology that determines which assets are eligible, how markets are selected, which prices are used, how constituents are weighted, and how the benchmark may change over time. CoinAPI's Indexes API provides several related datasets that help explain different aspects of an index.

Data Layer	Question It Answers
Index Value	What is the calculated index level?
Index OHLC Time-Series	How did the index level change over time?
Index Composition	Which assets were included in the index?
Constituent Weights	How much did each asset contribute?*
Index Input Data	Which market data and calculation inputs were associated with the index definition?
Index Definition Snapshots	What rules and configuration applied at a selected point in time?

* Availability of Composition Data, constituent weights, Index Definition Snapshots, and Index Input Data depends on the index family, calculation methodology, and supported datasets.

What Is Index Composition Data?

Index Composition Data describes what an index contains.

Depending on the index type and available dataset, composition-related information may include:

Index constituents
Constituent assets
Constituent weights
Historical composition
Point-in-time index structure
Rebalancing-related changes
Index definition snapshots

Related datasets, such as Index Definition Snapshots, may provide additional context about the configuration and methodology associated with an index at a specific point in time.

The calculated index value alone does not explain which of these events occurred. Composition Data provides the additional context needed to interpret benchmark performance.

What Is Index Input Data?

Index Input Data refers to the underlying information associated with an index definition and its calculation methodology.

Depending on the methodology and available dataset, it may include:

Asset prices and trading volumes
Average prices and market activity data
Reference asset conversions
Source-selection information
Rebalancing-related inputs
Other methodology-specific calculation data

Index Input Data is associated with an index_definition_id, allowing developers to inspect the calculation inputs for a supported index definition.

Because different methodologies use different calculation rules, the available input data can vary between index families and supported datasets. Confirm the exact relationship between an index_definition_id, its versioning, and the available input data in the current API documentation.

Comparison

Index Composition vs. Index Input Data

Composition data and input data describe different parts of the same index calculation process. Composition Data describes what the benchmark contained. Input Data describes which market data and calculation inputs were used to calculate a supported index definition.

If You Need to Know…	Use
Which assets are included in an index	Index Composition Data
How constituents are weighted*	Multi-Asset Weights
What an index contained historically	Historical Composition Data
What an index definition looked like at a specific point in time	Snapshot Data
Which market data contributed to a calculation	Index Input Data
Which exchanges or symbols were associated with the methodology	Index Input Data
How an index methodology uses market inputs	Index Input Data + methodology docs

* Available for supported multi-asset indexes. Many analytical workflows benefit from using both datasets together.

Current Weights, Historical Composition, and Point-in-Time Inputs

Index composition is not always static. Depending on the methodology, constituent assets, constituent weights, eligibility rules, and benchmark structure may change over time through scheduled reviews or rebalancing events. CoinAPI provides different datasets depending on the type of analysis being performed.

Current Constituent Weights

Use current constituent weights when you need to understand the latest allocation of a supported multi-asset index.

Typical use cases:

Live exposure monitoring
Portfolio benchmarking
Benchmark replication
Concentration analysis
Current risk monitoring

Current constituent weights are available for supported multi-asset indexes through dedicated endpoints. Historical composition, snapshot data, and related datasets depend on the index type and available API functionality.

Historical Composition

Where historical composition data is available, it can be used to reconstruct what an index contained at a specific point in time.

Typical applications:

Historical research
Performance attribution
Strategy backtesting
Audit workflows
Historical exposure analysis

Point-in-Time Input Data

Where supported, Index Input Data can help explain which market prices, trading volumes, exchanges, symbols, or other calculation inputs were associated with a historical index calculation.

Using historical composition together with historical input data helps avoid a common analytical mistake: explaining a historical index value using today's constituents, weights, or market inputs.

How Index Input Data Supports Different Methodologies

Different index methodologies use different calculation logic and may rely on different types of market data. As a result, the available Index Input Data can vary between methodologies and supported datasets. The following examples illustrate how different methodologies may use different inputs.

VWAP

VWAP (Volume-Weighted Average Price) methodologies use trading activity to determine how market prices contribute to an index value.

Relevant inputs may include:

Average prices
Trading volumes
Eligible exchanges
Eligible trading symbols
Reference asset conversions
Source selection
Filtering logic

These inputs can help explain how different markets contributed to a calculated benchmark.

PRIMKT

PRIMKT (Principal Market Price) methodologies determine a principal market based on qualifying trading activity before selecting the price used in the calculation.

Relevant inputs may include:

Eligible exchanges
Trading activity
Symbol-level volume
Last traded prices
Principal market selection
Source eligibility

These datasets can help users understand why a particular market was selected for a calculation.

CAPIVIX and Custom Methodologies

CoinAPI supports multiple index methodologies, including CAPIVIX, as well as custom index methodologies for Enterprise users.

Because different methodologies may use different source data, eligibility rules, calculation inputs, and rebalancing logic, Index Input Data should always be interpreted together with the relevant methodology documentation.

Endpoints

Index Composition and Input Data Endpoints

Composition-related information is available through several Indexes API datasets, including historical index data, supported multi-asset weight endpoints, and index definition snapshots where applicable. CoinAPI also provides dedicated Index Input Data endpoints.

Endpoint	Purpose
GET /indexdef/input-data/{index_definition_id}	Retrieve Index Input Data associated with a selected index definition.
GET /indexdef/input-data/{index_definition_id}/all	Retrieve the broader available Index Input Data associated with the selected index definition.

Both endpoints use index_definition_id, reflecting that input data is associated with an index definition rather than an individual calculated value. Confirm the exact response schema, supported fields, pagination behavior, timestamps, and the distinction between the base endpoint and the /all endpoint in the current API documentation before building a production integration.

Best Practices for Accurate Index Analysis

Use current constituent weights only when analyzing the latest structure of supported multi-asset indexes. Where historical composition data is available, use the composition that applied during the period being analyzed rather than assuming today's constituents and weights also applied historically.

When available, combine Index Composition Data with historical index values to better understand how changes in benchmark exposure affected performance over time. Review Index Input Data together with the relevant methodology documentation to understand how different calculation approaches use market data.

For VWAP-based methodologies, useful inputs may include:

Trading prices
Trading volumes
Eligible trading symbols
Source exchanges
Reference asset conversions
Source selection or filtering logic

For PRIMKT methodologies, useful inputs may include:

Eligible exchanges
Trading activity
Volume measurements
Principal market selection
Last traded prices

Because available datasets differ between index families and methodologies, always verify the supported endpoints, response schema, available fields, timestamps, and pagination behavior in the current API documentation before building production integrations.

Index Composition and Input Data

Build More Transparent Crypto Index Applications

Understanding a cryptocurrency index often requires more than retrieving its latest value.

Combine Index Composition Data and Index Input Data with CoinAPI's current index values, historical time series, OHLC data, and methodology documentation to build more transparent, explainable, and auditable cryptocurrency index workflows.