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

# Exchange New Listing

Triggers when a new trading pair or coin is listed on a supported exchange. Monitors Upbit, Binance, Bithumb, Coinbase, Revolut, and Hyperliquid for new listings in real-time. Useful for listing sniper bots, new coin alerts, or trading pair monitoring. Detects when exchanges add new tokens like BTC, ETH, or any newly listed cryptocurrency. Hyperliquid support includes HIP-3 deployer DEX markets.

Trigger Markets

Triggers when a new trading pair or coin is listed on a supported exchange. Monitors Upbit, Binance, Bithumb, Coinbase, Revolut, and Hyperliquid for new listings in real-time. Useful for listing sniper bots, new coin alerts, or trading pair monitoring. Detects when exchanges add new tokens like BTC, ETH, or any newly listed cryptocurrency. Hyperliquid support includes HIP-3 deployer DEX markets.

## At a Glance

| Field | Value |
| --- | --- |
| Trigger ID | `exchange-listing` |
| Category | Markets |
| Tags | `exchange`, `listing`, `trading`, `defi`, `alert`, `cex`, `hyperliquid`, `dex` |

## Trigger Configuration

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `exchange` | `string` | Yes | The exchange to monitor for new trading pair listings |

## Trigger Result

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `exchange` | `string` | Yes | The exchange where the new pair was listed \(e.g., upbit, binance, bithumb, revolut, hyperliquid\) |
| `symbol` | `string` | Yes | Normalized trading pair symbol \(e.g., BTC-USDT, BERA-KRW\) |
| `baseAsset` | `string` | Yes | The base asset of the trading pair \(e.g., BTC, BERA\) |
| `quoteAsset` | `string` | Yes | The quote asset of the trading pair \(e.g., USDT, KRW\) |
| `triggeredAt` | `string` | Yes | Timestamp when the new listing was detected \(UTC, RFC3339 format\) |
| `dex` | `string` | No | Hyperliquid deployer DEX identifier \(e.g., xyz, flx, vntl\). Empty for native HL markets and non-Hyperliquid exchanges. |
| `maxLeverage` | `integer` | No | Maximum leverage for the market \(Hyperliquid only, 0 for other exchanges\) |
| `onlyIsolated` | `boolean` | No | Whether the market only supports isolated margin \(Hyperliquid only, false for other exchanges\) |

## Workflow Root Example

```json
{
  "nodes": {
    "root": {
      "type": "exchange-listing",
      "payload": {
        "exchange": "upbit"
      },
      "children": [
        "log_event"
      ]
    },
    "log_event": {
      "type": "log",
      "payload": {
        "message": "Triggered at {{$trigger.triggeredAt}}"
      },
      "children": []
    }
  }
}
```

**Reference trigger output**

Downstream nodes can use `{{$trigger.triggeredAt}}` and any result fields listed above. Event triggers usually expose the raw source payload under a field such as `event`, `body`, `trade`, or `raw`.