Charting WebSocket

Messages

{
  "type": "event",
  "timestamp": "2026-02-23T18:36:59Z",
  "payload": {
    "type": "quotes",
    "symbol": "AAPL",
    "data": {
      "isDelayed": false,
      "quote": {
        "s": "ok",
        "n": "AAPL",
        "v": {
          "ch": 4.77,
          "chp": 1.8,
          "short_name": "AAPL",
          "exchange": "NASDAQ",
          "lp": 269.35,
          "ask": 269.36,
          "bid": 269.34,
          "open_price": 263.48,
          "high_price": 269.43,
          "low_price": 263.38,
          "prev_close_price": 264.58,
          "volume": 48234100
        }
      },
      "trade": {
        "s": "ok",
        "t": 1771871819,
        "lp": 269.35,
        "v": 100
      }
    },
    "timestamp": 1771871819072
  }
}

WSS

charts

What this stream is for. This WebSocket is a charting-specific feed designed to plug straight into the TradingView Charting Library or any chart widget that follows the TradingView data shape. If you’re rendering candlestick or line charts in your app and need them to update in real time, use this feed. If you need full market depth, Greeks, or T&S, use the Market Data WebSocket instead.

Key Features

Connect Then Authenticate

Open a WebSocket to the endpoint, then send a request to POST /auth with your token. Subscribe only after authSuccess.

Real-Time Quotes

Stream live bid/ask, last price, OHLC, volume, and change for charting.

Real-Time Trades

Receive last-trade updates (price, size, timestamp) for tape and chart integration.

Subscribed Quotes

Subscribe to one or more symbols; receive event messages with quote and trade data for each subscribed symbol.

TradingView Format

Quote and trade payloads use TradingView-friendly field names for easy integration.

Equities & Options

Support for stock tickers and OSI option symbols.

Keep-Alive

Ping/pong for connection health; optional correlation ID for pong.

Connection Details

Endpoint

Connect to the WebSocket at /v1/charts/ws.Production: wss://api.aries.com/v1/charts/ws
Staging: wss://api.aries.com/v1/charts/wsHealth check: GET /tv/health (HTTP)

Authentication

Authentication is required. Use an OAuth2 access token (e.g. from POST /v1/oauth2/token). After the connection is open, send a request message with method POST, path /auth, and body { "token": "<your_access_token>" }. Wait for a response with action authSuccess before sending subscribe messages. If the server returns authRequired or error, authentication failed (e.g. invalid or expired token).

This WebSocket follows a TradingView-compatible message format. All request/response messages use the shared envelope: type, id, payload (with method, path, body for requests).

Supported Symbols

Equities

Standard stock ticker symbols (e.g., AAPL, MSFT, GOOGL, TSLA). Use them exactly as a brokerage screen would display them.

Options

Option contracts use OSI (Options Symbology Initiative) symbols. Format: ROOT + YYMMDD + C/P + strike-in-cents (e.g., AAPL240119C00150000 is the AAPL Jan-19-2024 $150 Call).

Message Envelope

Every message you send or receive uses the same outer JSON shape:

Field	Type	Required	What to put here
`type`	string	Yes	What kind of message this is. Sent by you: `request` (RPC-style call, e.g. auth), `subscribe`, `unsubscribe`, `ping`. Sent by the server: `event` (streaming push), `response` (reply to your request), `pong` (reply to your ping).
`id`	string	No	A correlation ID you choose, like `"sub-aapl-1"`. The server echoes it back in the matching response/event so you can pair them up.
`timestamp`	string	No	RFC3339 timestamp (e.g. `2026-05-13T10:30:00Z`). Optional on client messages; the server fills it in on outbound messages.
`payload`	object	Yes	The actual body of the message. Shape depends on `type` — see the sections below.

Data Types

The subscription payload.type controls what kind of data the server streams back:

quotes (default) — Bid/ask, last price, OHLC, volume, change, and change percent. This is what most chart widgets need for the price/quote display.
bars — Accepted as a subscription type, but the server currently streams the same quotes-shaped quote/trade events for a bars subscription. It does not emit distinct OHLC bar/candle objects, resolutions, or intervals today. Use quotes unless you have a specific reason to send bars.

Use Cases

Live Chart Updates

Display real-time price movements on interactive charts.

TradingView Widgets

Feed real-time data into TradingView charting library or embedded widgets.

Quote Displays

Show last price, bid/ask, and volume in chart widgets (after authenticating).

Technical Analysis

Provide data for indicators and overlays in charting tools.

Connection

Connect to the Charting WebSocket the same way you would the Market Data WebSocket: establish the connection, then authenticate, then subscribe to symbols to receive real-time quotes and trades.

Connect to the endpoint

Open a secure WebSocket connection to:

wss://api.aries.com/v1/charts/ws

Authenticate

Immediately after the connection is open, send one request message to authenticate. Do not send subscribe messages until you receive a successful auth response. Send the following auth message:

{
  "type": "request",
  "id": "auth-001",
  "payload": {
    "method": "POST",
    "path": "/auth",
    "body": {
      "token": "YOUR_ACCESS_TOKEN"
    }
  }
}

Server responds (success): type: "response", with payload.action: "authSuccess", optional payload.id (echoed from request), payload.timestamp (Unix milliseconds), and payload.data.expiresIn (session expiry in milliseconds). Server responds (failure): payload.action: "authRequired" or payload.action: "error" with payload.error (e.g. “token is required”, “authentication failed”). Reconnect or send a new auth request with a valid token. After authSuccess, send subscribe messages to start receiving quote and trade event messages for the requested symbols. See Subscribing to Chart Data below.

Subscribing to Chart Data

After you have connected and authenticated, you can subscribe to real-time quotes (and trades) for one or more symbols. Each subscription uses a subscribe message; the server then sends event messages containing quote/trade data for those symbols.

Basic subscription structure

Send a subscribe message with type fixed as "subscribe", any id you want (used to correlate the server’s responses), and a payload describing what you want to receive:

Payload field	Type	Required	What to enter
`type`	string	No	`"quotes"` (default when omitted) for real-time price ticks. `"bars"` is accepted but currently returns the same `quotes`-shaped events (see Data Types above).
`symbol`	string	Yes	The instrument identifier — a stock ticker like `"AAPL"`, or an OSI option symbol like `"AAPL240119C00150000"`.
`symbolType`	string	No	`"symbol"` or `"option"`. Currently accepted but ignored by the server — it has no effect on the data returned.

Full message to send:

{
  "type": "subscribe",
  "id": "sub-1",
  "payload": {
    "type": "quotes",
    "symbol": "AAPL"
  }
}

Subscription examples

Single symbol (quotes)

Subscribe to real-time quotes for one equity:

{
  "type": "subscribe",
  "id": "sub-1",
  "payload": { "type": "quotes", "symbol": "AAPL" }
}

You will receive event messages with payload.type: "quotes" and payload.symbol: "AAPL" containing payload.data.quote and payload.data.trade.

Multiple symbols (quotes)

Subscribe to quotes for several symbols by sending one subscribe message per symbol (each with its own id if needed):First symbol:

{
  "type": "subscribe",
  "id": "sub-aapl",
  "payload": { "type": "quotes", "symbol": "AAPL" }
}

Second symbol:

{
  "type": "subscribe",
  "id": "sub-msft",
  "payload": { "type": "quotes", "symbol": "MSFT" }
}

Third symbol:

{
  "type": "subscribe",
  "id": "sub-googl",
  "payload": { "type": "quotes", "symbol": "GOOGL" }
}

The server sends event messages for each subscribed symbol; use payload.symbol to route updates.

Option contract (quotes)

For option contracts, use the OSI symbol:

{
  "type": "subscribe",
  "id": "sub-opt-1",
  "payload": { "type": "quotes", "symbol": "AAPL240119C00150000" }
}

Another equity (quotes)

{
  "type": "subscribe",
  "id": "sub-2",
  "payload": { "type": "quotes", "symbol": "TSLA" }
}

Connection Flow

Connect

Open a WebSocket connection to wss://api.aries.com/v1/charts/ws

Authenticate

Send a request message: type: "request", payload: { "method": "POST", "path": "/auth", "body": { "token": "<access_token>" } }. Wait for a response with payload.action: "authSuccess".

Send subscribe messages with payload.type and payload.symbol for each symbol you want.

Receive events

Process event messages containing quote and trade data for your subscribed symbols.

Unsubscribe (optional)

Send unsubscribe with the same symbol to stop updates.

Keep-Alive (optional)

Send ping periodically; server responds with pong.

Client → Server Messages

Provide payload.type and payload.symbol; the full message is built as:

{
  "type": "subscribe",
  "id": "sub-1",
  "payload": {
    "type": "quotes",
    "symbol": "AAPL"
  }
}

Unsubscribe

Stop receiving updates for a symbol. Only payload.symbol is required — the server unsubscribes by symbol, so payload.type is not needed and is ignored.

{
  "type": "unsubscribe",
  "id": "unsub-1",
  "payload": {
    "type": "quotes",
    "symbol": "AAPL"
  }
}

Ping

Keep-alive; server responds with pong. Optional id is echoed in the pong.

{ "type": "ping", "id": "ping-1" }

Server → Client Messages

Event (quote/trade update)

Server pushes quote and/or trade data for subscribed symbols.

{
  "type": "event",
  "timestamp": "2026-02-23T18:36:59Z",
  "payload": {
    "type": "quotes",
    "symbol": "AAPL",
    "data": {
      "isDelayed": false,
      "quote": {
        "s": "ok",
        "n": "AAPL",
        "v": {
          "ch": 4.77,
          "chp": 1.80,
          "short_name": "AAPL",
          "exchange": "NASDAQ",
          "description": "Apple Inc.",
          "lp": 269.35,
          "ask": 269.36,
          "bid": 269.34,
          "open_price": 263.48,
          "high_price": 269.43,
          "low_price": 263.38,
          "prev_close_price": 264.58,
          "volume": 48234100.00
        }
      },
      "trade": {
        "s": "ok",
        "t": 1771871819,
        "lp": 269.35,
        "v": 100
      }
    },
    "timestamp": 1771871819072
  }
}

The field names below (ch, chp, lp, n, v, etc.) are TradingView’s short-form keys. They look cryptic but they’re standardized — the TradingView Charting Library expects exactly these names. Do not rename them in your handler if you’re piping data into a TradingView widget.

Event payload fields:

Field	Type	Description
`type`	string	Always `"quotes"` for quote/trade events.
`symbol`	string	The symbol this event is about (e.g. `AAPL`). Match against your active subscriptions.
`data`	object	The quote and trade payload (see below).
`timestamp`	integer	When the event was emitted, in Unix milliseconds.

payload.data fields:

Field	Type	Description
`quote`	object	Quote data. Contains `s` (status string, usually `"ok"`), `n` (the symbol), and `v` (the actual quote values — see next table).
`trade`	object	Trade data (see below). Omitted if there’s no recent trade to report.
`isDelayed`	boolean	Indicates whether the feed is delayed. The server currently always sends `false` (real-time); treat `true` as reserved for future use.

payload.data.quote.v fields — these are the values the chart actually plots. All numbers and all optional (only changed fields may be present in an update):

Field	Type	What it represents
`ch`	number	Change — net price change from previous close (today’s last price − yesterday’s close). Drives the +/− indicator on a chart.
`chp`	number	Change percent — `ch` expressed as a percent of previous close.
`short_name`	string	Display ticker, e.g. `"AAPL"`.
`exchange`	string	Primary listing exchange, e.g. `"NASDAQ"`.
`lp`	number	Last price — most recent trade price. The number on the big “current price” label.
`ask`	number	Best ask (the lowest price someone is willing to sell at).
`bid`	number	Best bid (the highest price someone is willing to pay).
`open_price`	number	Today’s opening price (first trade of the session).
`high_price`	number	Today’s highest price so far.
`low_price`	number	Today’s lowest price so far.
`prev_close_price`	number	Yesterday’s closing price — the baseline for calculating today’s change.
`volume`	number	Cumulative number of shares traded today.

payload.data.trade fields — emitted whenever a new print appears on the tape:

Field	Type	What it represents
`s`	string	Status — `"ok"` when the trade is valid.
`t`	integer	Trade timestamp in Unix seconds (note: trade `t` is seconds, but the outer `payload.timestamp` is milliseconds).
`lp`	number	Last trade price — the price the trade printed at.
`v`	integer	Trade size (number of shares/contracts).

Response (auth or error)

Auth success: type: "response", payload.action: "authSuccess", optional payload.id (echoed request ID), payload.timestamp (Unix milliseconds), payload.data.expiresIn (session expiry in milliseconds). Error (e.g. invalid subscribe): type: "response", payload.error with message.

{
  "type": "response",
  "id": "sub-1",
  "payload": {
    "error": "symbol is required in payload",
    "timestamp": 1736946600123
  }
}

Pong

Reply to ping.

{
  "type": "pong",
  "id": "ping-1",
  "timestamp": "2025-01-15T14:30:00Z"
}

Quick Start Example

Connect, authenticate, then subscribe to quotes (same pattern as the Market Data WebSocket):

const ws = new WebSocket('wss://api.aries.com/v1/charts/ws');

ws.onopen = () => {
  // 1. Authenticate first
  ws.send(JSON.stringify({
    type: 'request',
    id: 'auth-001',
    payload: {
      method: 'POST',
      path: '/auth',
      body: { token: 'YOUR_OAUTH2_ACCESS_TOKEN' }
    }
  }));
};

ws.onmessage = (event) => {
  const msg = JSON.parse(event.data);

  if (msg.type === 'response' && msg.payload?.action === 'authSuccess') {
    // 2. After auth success, subscribe to quotes
    ws.send(JSON.stringify({
      type: 'subscribe',
      id: 'sub-1',
      payload: { type: 'quotes', symbol: 'AAPL' }
    }));
  } else if (msg.type === 'event' && msg.payload?.data) {
    const { quote, trade } = msg.payload.data;
    if (quote?.v) console.log('Quote:', quote.v.lp, quote.v.ch, quote.v.volume);
    if (trade) console.log('Trade:', trade.lp, trade.v, trade.t);
  } else if (msg.type === 'response' && msg.payload?.error) {
    console.error('Error:', msg.payload.error);
  } else if (msg.type === 'pong') {
    console.log('Pong received');
  }
};

// Optional keep-alive
const pingInterval = setInterval(() => {
  if (ws.readyState === WebSocket.OPEN) {
    ws.send(JSON.stringify({ type: 'ping', id: 'ping-1' }));
  }
}, 30000);

ws.onclose = () => clearInterval(pingInterval);

Support

Need help with the Charting WebSocket?

Email Support

dev@aries.com

API Status

status.aries.com

Messages

{
  "type": "event",
  "timestamp": "2026-02-23T18:36:59Z",
  "payload": {
    "type": "quotes",
    "symbol": "AAPL",
    "data": {
      "isDelayed": false,
      "quote": {
        "s": "ok",
        "n": "AAPL",
        "v": {
          "ch": 4.77,
          "chp": 1.8,
          "short_name": "AAPL",
          "exchange": "NASDAQ",
          "lp": 269.35,
          "ask": 269.36,
          "bid": 269.34,
          "open_price": 263.48,
          "high_price": 269.43,
          "low_price": 263.38,
          "prev_close_price": 264.58,
          "volume": 48234100
        }
      },
      "trade": {
        "s": "ok",
        "t": 1771871819,
        "lp": 269.35,
        "v": 100
      }
    },
    "timestamp": 1771871819072
  }
}

Sign-in Request

type:object

Subscribe Request

type:object

Subscribe to quotes/trades for a symbol

Unsubscribe Request

type:object

Unsubscribe from a symbol

Ping Request

type:object

Keep-alive ping

Quote/Trade Event

type:object

Server-pushed quote and/or trade update

Error Response

type:object

Error response for subscribe/unsubscribe or auth

Auth Required Response

type:object

Server requests authentication

Auth Success Response

type:object

Successful authentication response

Pong Response

type:object

Pong reply to ping

Market Data WebSocket Account Updates WebSocket

Overview

WebSockets

Charting WebSocket

Connect Then Authenticate

Real-Time Quotes

Real-Time Trades

Subscribed Quotes

TradingView Format

Equities & Options

Keep-Alive

Endpoint

Authentication

Equities

Options

Live Chart Updates

TradingView Widgets

Quote Displays

Technical Analysis

Connection

Connect to the endpoint

Authenticate

Subscribing to Chart Data

Basic subscription structure

Subscription examples

Connection Flow

Client → Server Messages

Unsubscribe

Ping

Server → Client Messages

Event (quote/trade update)

Response (auth or error)

Pong

Quick Start Example

Support

Email Support

API Status

Connect Then Authenticate

Real-Time Quotes

Real-Time Trades

Subscribed Quotes

TradingView Format

Equities & Options

Keep-Alive

​Endpoint

​Authentication

​Equities

​Options

Live Chart Updates

TradingView Widgets

Quote Displays

Technical Analysis

​Connection

​Connect to the endpoint

​Authenticate

​Subscribe to symbols

​Subscribing to Chart Data

​Basic subscription structure

​Subscription examples

​Connection Flow

​Client → Server Messages

​Subscribe

​Unsubscribe

​Ping

​Server → Client Messages

​Event (quote/trade update)

​Response (auth or error)

​Pong

​Quick Start Example

​Support

Email Support

API Status

Endpoint

Authentication

Equities

Options

Connection

Connect to the endpoint

Authenticate

Subscribe to symbols

Subscribing to Chart Data

Basic subscription structure

Subscription examples

Connection Flow

Client → Server Messages

Subscribe

Unsubscribe

Ping

Server → Client Messages

Event (quote/trade update)

Response (auth or error)

Pong

Quick Start Example

Support