Exchange-traded funds (ETFs) have become an important part of modern financial markets. They allow investors to gain exposure to stocks, bonds, commodities, and other assets through a single exchange-traded product. However, building an ETF tracking platform, investment dashboard, or trading application requires more than displaying the latest market price. Developers also need access to trading volume, net asset value (NAV), indicative net asset value (IOPV), and premium or discount information.
An ETF API helps developers collect and integrate this information into financial applications. With the right data infrastructure, applications can monitor ETF prices, compare market values with underlying asset estimates, and identify unusual price differences throughout the trading session.
In this guide, we explore the essential ETF data points, explain how premium and discount monitoring works, and discuss how developers can use iTick’s fund market data services to build more informative ETF applications.
Understanding ETF Market Data
An ETF trades on an exchange like an ordinary stock, but its value is connected to a portfolio of underlying securities or other assets. This creates two important values that investors should understand:
- Market price: The price at which ETF shares are currently trading on an exchange.
- Net asset value (NAV): The value of the fund’s underlying assets minus its liabilities, divided by the number of outstanding shares.
These values are related but do not always match. Supply and demand, market liquidity, trading hours, and changes in the underlying portfolio can cause an ETF to trade above or below its estimated underlying value.
For developers, access to reliable market data makes it easier to monitor these differences and present meaningful information to users.
Essential Data Points for ETF Monitoring
An effective ETF monitoring application should combine several market indicators instead of relying on a single price field.
1. Real-Time ETF Quotes
Real-time quotes provide the latest available trading information for an ETF. Common fields include:
- Latest traded price
- Opening price
- Previous closing price
- Daily high and low
- Trading volume
- Trading amount
- Price change and percentage change
- Trading status
These fields help investors understand how an ETF is performing during the trading session.
For example, a portfolio dashboard can display the latest prices of multiple ETFs, calculate daily performance, and highlight products experiencing unusual trading activity.
2. Net Asset Value (NAV)
NAV represents the underlying value of a fund’s assets after subtracting liabilities. It is an important reference point when evaluating whether an ETF is trading close to its estimated value.
However, NAV is not necessarily updated continuously during market hours. Many funds calculate and publish official NAV at specific intervals, often at the end of the trading day.
Applications should therefore distinguish between official NAV and intraday estimates rather than presenting them as interchangeable values.
3. Indicative Net Asset Value (IOPV)
Indicative Optimized Portfolio Value (IOPV) provides an estimated intraday value of an ETF’s underlying portfolio.
It can help investors compare the ETF’s current market price with an estimated portfolio value while the exchange is open.
IOPV is particularly useful for:
- Intraday premium and discount monitoring.
- ETF price comparison.
- Portfolio valuation dashboards.
- Market analysis tools.
- Identifying potential pricing inefficiencies.
IOPV is an estimate, not a guaranteed executable price or a replacement for official NAV. Its availability and calculation methodology can also vary by market and fund.
4. Trading Volume and Market Activity
Trading volume indicates how many ETF shares have changed hands during a particular period. Combined with price information, it can help users evaluate market participation and liquidity.
Developers can use historical and current volume information to build charts, identify unusual activity, and compare trading patterns across different ETFs.
5. Historical Prices and Market Depth
Historical prices help investors evaluate ETF performance over different periods, while market depth provides information about available buying and selling interest.
Together, these data points support more advanced applications, including trading analytics, portfolio monitoring, and quantitative research.
How iTick Supports ETF Data Integration
Developers looking for fund market data need an infrastructure that supports both individual requests and continuous market updates.
The iTick fund data service provides access to ETF and other fund market information through REST and WebSocket interfaces. Its documentation covers US, Hong Kong, Shanghai, Shenzhen, Japanese, and Korean market regions.
Key capabilities include:
- Real-time fund quotes.
- Batch ETF quote requests.
- Latest trading prices and percentage changes.
- Trading volume and trading amounts.
- IOPV estimates.
- Tick-by-tick transaction information.
- Order book depth.
- Historical and candlestick data.
The REST endpoint for batch fund quotes is:
GET https://api.itick.org/fund/quotes?region=US&codes=QQQ,IEF
Requests use a token in the HTTP header for authentication.
A basic Python implementation looks like this:
import requestsurl = “https://api.itick.org/fund/quotes”headers = { “accept”: “application/json”, “token”: “YOUR_API_TOKEN”}params = { “region”: “US”, “codes”: “QQQ,IEF”}response = requests.get( url, headers=headers, params=params)if response.status_code == 200: print(response.json())else: print(“Error:”, response.status_code)
This example retrieves quote information for QQQ and IEF in a single request. Developers can use the returned JSON data to populate ETF watchlists, portfolio dashboards, and market monitoring interfaces.
The documented response includes the latest price, opening price, previous close, daily high and low, volume, trading amount, timestamp, and percentage change. The separate fund WebSocket service supports streaming quotes, trades, and order book updates.
Mutual Fund Prices – iTick+1
Calculating ETF Premiums and Discounts
One of the most useful features of an ETF monitoring platform is the ability to compare its exchange price with its estimated underlying value.
An ETF may trade at a premium when its market price is higher than its NAV or IOPV. Conversely, it trades at a discount when its market price falls below the reference value.
The following formula calculates the premium or discount percentage:
\[ \text{Premium/Discount (\%)} = \frac{\text{Market Price}-\text{NAV}} {\text{NAV}}\times100 \]
Consider a hypothetical ETF with these values:
| Metric | Value |
| Market price | $105.50 |
| Estimated NAV | $104.00 |
| Difference | $1.50 |
| Premium | 1.44% |
The ETF is trading at approximately 1.44% above its estimated NAV.
A monitoring application can automatically calculate this percentage whenever updated market and valuation data become available.
For reliable results, developers should ensure that both values use compatible timestamps, currencies, and valuation conventions. They should also distinguish between official NAV and intraday IOPV.
Using WebSocket for Continuous ETF Monitoring
REST APIs are useful when applications need individual quotes, periodic updates, or historical information. However, repeatedly requesting the same information can create unnecessary network traffic.
WebSocket connections provide an alternative by delivering market updates as they become available.
The iTick fund WebSocket endpoint is:
wss://api.itick.org/fund
For example, developers can subscribe to ETF quote updates using:
{
“ac”: “subscribe”,
“params”: “QQQ$US,SPY$US”,
“types”: “quote”
}
The subscription format allows applications to monitor multiple fund symbols through one connection.
Depending on the subscription and data permissions, developers can request:
- quote for real-time quotes.
- tick for trade information.
- depth for order book updates.
- kline for candlestick information.
The documented fund WebSocket interface supports up to 500 symbols per connection, subject to account and subscription restrictions. Developers should also implement heartbeat handling, reconnection logic, and message processing to maintain reliable connections.
Global Coverage – iTick
Building an ETF Premium and Discount Dashboard
Combining quotes, valuation estimates, and historical information makes it possible to develop a comprehensive ETF monitoring dashboard.
A practical dashboard can include the following components:
1. ETF Watchlist
Display selected ETFs with their latest market prices, daily percentage changes, and trading volumes.
2. NAV Comparison
Show official NAV and intraday IOPV separately, including the timestamp of each valuation.
3. Premium/Discount Indicator
Calculate the percentage difference between the latest market price and the selected valuation reference.
4. Historical Performance Charts
Use historical price information to visualize ETF movements over different periods.
5. Market Activity Monitoring
Display trading volume, transaction activity, and order book depth to help users understand market conditions.
6. Automated Alerts
Configure notifications when an ETF’s premium or discount crosses a predefined threshold.
For example, an application might notify users when an ETF trades more than 1.5% above its estimated NAV. These alerts are monitoring features, not automatic indications that a trading opportunity exists.
Important Considerations When Choosing an ETF Data Provider
Not every market data provider offers the same coverage, update frequency, or valuation information. Before integrating a service, developers should evaluate several factors.
- Market coverage: Check whether the provider supports the exchanges and ETF symbols required by your application.
- Data freshness: Understand how frequently quotes and valuation estimates are updated.
- NAV availability: Confirm whether the service provides official NAV, IOPV, or both.
- API performance: Evaluate response times, rate limits, and WebSocket stability.
- Historical information: Check whether historical prices and trading information are available.
- Documentation: Look for clear authentication instructions, response examples, and integration guides.
- Licensing: Review exchange permissions and redistribution requirements, especially for commercial applications.
These considerations help prevent problems such as displaying outdated valuations, comparing incompatible timestamps, or exceeding subscription limits.
Conclusion
Building a reliable ETF monitoring platform requires access to more than basic price information. Developers need market quotes, trading volume, historical prices, valuation references, and continuous updates to provide meaningful insights into ETF performance.
An ETF API can simplify the integration of these data points into financial dashboards, investment applications, and analytical platforms.
With REST and WebSocket fund data services, iTick provides developers with tools for retrieving ETF quotes, monitoring trading activity, and accessing supported IOPV information. Its fund data infrastructure can serve as a useful starting point for applications that require structured market information across multiple regions.
Before launching a commercial application, developers should verify the availability of specific valuation fields, exchange coverage, subscription permissions, and data redistribution rights.