> ## Documentation Index
> Fetch the complete documentation index at: https://docs.amberdata.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Asset Symbols FAQ

### What Are .amb.-Suffixed Symbols?

In Amberdata’s aggregated metric endpoints (e.g., VWAP, TWAP, volume metrics), asset symbols may appear with an `.amb.` suffix followed by an integer (e.g., `gas.amb.1`). This suffixing system is used to disambiguate **asset collisions** across exchanges—cases where multiple unrelated assets share the same symbol.

An **asset collision** occurs when two or more distinct assets are listed under the same symbol on different exchanges. For example:

* **Neo Gas** is listed under the symbol `GAS` on Poloniex, HTX, OKEX, and Binance.
* **Gas DAO** also uses the symbol `GAS` but is listed on MEXC.

Both assets trade under the instrument `gas_usdt`, but they represent entirely different entities with different market behaviors and valuations. Aggregating metrics such as VWAP or trading volume without resolving this conflict would produce inaccurate results.

To handle this, Amberdata appends an `.amb.` suffix and a unique identifier (e.g., `gas.amb.1`, `gas.amb.2`) to differentiate these assets in aggregated metric endpoints.

### **Using Aggregated Metric Features**

To correctly use aggregated metrics:

* Query the **aggregated metrics information endpoints** to retrieve supported asset symbols and names.
* These endpoints return metadata that maps the `.amb.`-suffixed asset to its corresponding exchange-specific representations.

### **Tick-by-Tick Market Data vs Aggregated Metrics**

* **Tick-by-Tick Market Data** (trades, order book events/snapshots) uses **the exact asset symbol as listed on the exchange** (e.g., `lsd7` on MEXC).
* **Aggregated Metrics** (VWAP, TWAP, trading volumes) use **normalized and disambiguated symbols**, which may include the `.amb.` suffix.

**Important:** `.amb.`-suffixed symbols are not supported for tick-by-tick endpoints. Use the exchange-specific symbol instead.

***

### **Why Aggregated Metrics May Be Temporarily Unavailable**

Amberdata employs a **human-in-the-loop asset verification process** to ensure the accuracy of aggregated metrics. When a new asset or instrument is listed:

* Raw market data becomes available immediately (including trades and order book events).
* Aggregated metrics become available only after the asset is reviewed and classified by Amberdata’s internal asset review committee.

This verification process typically introduces a delay of up to **\~1 week** before aggregated metrics (VWAP, TWAP, etc.) are published for newly listed assets.

***

### I'm able to pull raw market data for an asset/instrument that recently got listed on an exchange, but I'm not able to get VWAP, TWAP, or other aggregated metrics for the asset/instrument?

Amberdata applies a **human-in-the-loop asset review process** to verify whether newly listed instruments represent existing assets or entirely new ones. This process includes automated detection but concludes with manual validation by internal subject matter experts.

As a result:

* **Tick-by-tick market data** (e.g., trades, order book events, snapshots) is made available immediately upon asset listing.
* **Aggregated metrics** (e.g., VWAP, TWAP, volume) are only enabled after the asset classification is completed.

This review process typically results in a delay of approximately **1 week** from the time of listing to the availability of aggregated metrics.

### Will the `.amb.` suffixed symbol work for tick-by-tick market data features?

No, the `.amb.` suffixed symbols only work for the aggregated metrics. For tick-by-tick data (e.g., trades, order book events, order book snapshots), use the **original exchange-specific asset symbol**, which matches the naming convention used by the exchange.

* Use the **aggregated metrics information endpoints** to retrieve metadata for disambiguated symbols.
* These responses include mappings of `.amb.` symbols to the corresponding native symbols per exchange.

For example:

<CodeGroup>
  ```json JSON theme={null}
  {
    "status": 200,
    "title": "OK",
    "description": "Successful request",
    "payload": {
      "metadata": {
        "next": null
      },
      "data": [
        {
          "asset": "lsd",
          "startDate": 1708387200000,
          "endDate": 1708628220000,
          "assetName": "L7 DEX",
          "marketDataReference": [
            {
              "exchange": "huobi",
              "assetSymbol": "lsd"
            },
            {
              "exchange": "mexc",
              "assetSymbol": "lsd7"
            }
          ]
        }
      ]
    }
  }
  ```
</CodeGroup>

In this example:

* The asset **L7 DEX** has the symbol `lsd` on HTX and `lsd7` on MEXC.
* For aggregated metrics, use the `.amb.`-style symbol.
* For tick-by-tick data, use the exact exchange-specific symbol (e.g., `lsd7` on MEXC).

In order to reduce confusion when using the tick-by-tick market data features, for a given asset, **A**, Amberdata retains the exact symbol of **A** from each exchange for the instruments of **A**. Remember, an asset symbol is unique to a single exchange, but it is not unique across exchanges.

***