Choosing a Gold Price API: Is International Gold Enough for a Gold ETF Tool?

TickDB Research ·

Choosing a Gold Price API: Is International Gold Enough for a Gold ETF Tool?

Abstract: A gold ETF page needs more than an international gold quote. Using actual 518880.SH and XAUUSD responses alongside exchange and fund-manager information, this article separates ETF trade prices, international gold references and fund NAV, and provides a product-input checklist plus a reproducible holding-value calculation.

“Show gold, show my holding value, show today's change” sounds like one small product requirement. It is several data requirements. An international gold quote can keep changing at night while a domestic ETF record remains timestamped in the afternoon. The fund manager's NAV is another input again.

One page-wide “updated now” label can make those different numbers appear synchronized.

Start with the actual fund

The Shanghai Gold Exchange lists fund 518880, Huaan Yifu Gold ETF, against the closing price of its Au99.99 contract. Huaan's product page identifies code 518880 and currency CNY, and separately publishes unit NAV.

A holding-value feature needs the ETF's own per-share price. International gold is relevant market context, but it is not a substitute for that fund-share price. The World Gold Council likewise distinguishes spot, LBMA benchmark and regional prices.

Two records from one request had different times

On November 16, 2026, one TickDB snapshot request for 518880.SH,XAUUSD returned:

ObjectRaw latest-price fieldData time, UTC+8
518880.SH, Huaan gold ETF7.852November 16, 15:00:01
XAUUSD, gold/US dollar3873.51000November 16, 23:19:09

The timestamps were 8 hours, 19 minutes and 8 seconds apart. They are unsuitable for an unqualified same-instant performance comparison. They do show why each number needs its own time label.

The ETF and international gold reference have separate identities and data times

This figure presents two archived quote objects, not synchronized returns. Their scales and timestamps differ.

Keep request receipt time in operational records. On the product page, show the ETF timestamp beside the ETF price and the international quote timestamp beside its own number. Determine market status using the relevant calendar and sessions; timestamp separation alone does not diagnose an API fault.

Which price values 1,000 ETF shares?

For a teaching holding of 1,000 shares, the archived ETF price gives:

1,000 shares × CNY7.852 per share = CNY7,852.00

This is a reference market value at that quote's timestamp, before fees, not a guaranteed liquidation amount. Holding profit or loss additionally requires cost basis and the applicable fee treatment.

Multiplying XAUUSD by 1,000 ETF shares mixes different units. Currency conversion alone does not turn a fund share into a fixed quantity of gold.

from decimal import Decimal
etf_price = Decimal("7.852")  # Archived 518880.SH quote
teaching_shares = Decimal("1000")
print(f"CNY {etf_price * teaching_shares:.2f}")
CNY 7852.00

NAV is another product requirement

During the same evening's check, Huaan's official page displayed November 16 unit NAV of 7.8814, whereas the archived latest trade-price field was 7.852. These are different data objects, rather than an automatic indication that one source is wrong.

An intraday premium/discount feature needs an appropriate reference input and calculation convention, including a verified IOPV source where relevant. A NAV published in the evening must not be treated as information already available at every earlier intraday moment.

User taskRequired inputsCan an international gold quote do it alone?
View this ETF's priceETF identity, per-share quote and timestampNo
Value a fixed share holdingShares, ETF quote and currencyNo
Observe international goldDefined price object, units and timestampAs corresponding market context
Calculate holding P&LQuote, shares, cost and feesNo
Show NAV or an intraday premium/discountSuitable NAV/IOPV, time and methodNo

TickDB's specific role in this example was to supply A-share ETF and gold/US-dollar quote inputs through one REST snapshot endpoint while retaining separate identities and timestamps. That can simplify querying; it does not establish NAV, IOPV or a complete fund-valuation service.

Because the main task is a domestic ETF page, the TickDB A-share market data page is the relevant next step. List fund valuation, fees and subscription/redemption information separately when the product needs them.

Before comparing gold API suppliers, write one sentence for each number on the page: what decision should this number help the reader make? The answer determines the input to buy.

Sources: Shanghai Gold Exchange gold ETF list; Huaan 518880 product page; World Gold Council “Gold spot prices”; TickDB snapshot documentation and November 16, 2026 raw response. All holding quantities are teaching assumptions.

Related articles

Choosing a Hong Kong Stock Quote API: What Changes When a Script Moves to a Server?

Moving a personal Hong Kong stock script to a team server requires more than comparing API prices. Using Futu OpenD's official operating conditions and one actual Tencent quote response, this article separates gateway maintenance, login, quote entitlements, data timestamps and intended use into a practical trial checklist.

TickDB Research ·

Choosing a US Historical Stock Data API: When Does a Backtest Need Minute Bars?

Historical data should match the information a backtest needs. Using AAPL daily data and 390 one-minute records from the same day, this article checks the order of two price-threshold observations, explains when daily bars can be sufficient, and shows how an unresolved volume discrepancy changes a data trial.

TickDB Research ·

How to Choose an A-Share Market Data API: Is One Successful Stock Query Enough for Market-Wide Screening?

For quantitative teams and tool owners extending end-of-day research into intraday stock screening, this guide compares specific AKShare, Tushare and TickDB interfaces. A real response containing 8,209 records illustrates how security scope, field units and update methods affect market-wide screening, historical research and candidate monitoring. It ends with a trial order and a completed decision card that research and engineering colleagues can use together.

TickDB Research ·

How to Choose a US Stock Data API: What Is Worth Paying for, from Daily Backtests to Premarket Monitoring?

For small teams using Python to backtest US stocks and maintain research watchlists, this guide compares yfinance, Alpha Vantage and TickDB. Official documentation and a real archived snapshot show when an existing free workflow is sufficient, which premarket requirements may justify paid access, and what to verify before a trial. The aim is to connect data capabilities, access conditions and integration work to an actual research task.

TickDB Research ·

Yahoo Finance API Migration: Align Your Existing Data Before Switching Stock APIs

For financial product owners evaluating a replacement for a Yahoo Finance or yfinance prototype, a migration decision needs more than a successful request. This guide explains adjustment and date differences, compares old and new records, and connects findings to existing features. It includes an offline Python comparison tool, a browser-readable report, and an acceptance worksheet. A clearly labelled synthetic example demonstrates the decision process; the existing TickDB live sample is presented separately.

TickDB Research ·