Recent Updates

Watchlist Endpoints

Added five watchlist endpoints under two new OAuth2 scopes, watchlist:information (read) and watchlist:management (write), and moved the existing Delete Watchlist endpoint onto watchlist:management.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v1/config/watchlist	Watchlist	Added; lists every watchlist owned by the user as `{ user_id, watchlist: [{ id, name, symbols, invalid_symbols }] }`. Returns `500` rather than an empty list if the user has no watchlist. Scope: `watchlist:information`.
GET /v1/config/watchlist/{watchlist_id}	Watchlist	Added; returns one watchlist (`{ id, name, symbols, invalid_symbols }`). Errors: `400`, `404`. Scope: `watchlist:information`.
POST /v1/config/watchlist	Watchlist	Added; creates a watchlist from `name` (required, unique per user) and optional `symbols`. Symbols are uppercased, de-duplicated, and validated; unresolvable symbols are dropped and returned in `invalid_symbols` instead of failing the request. Returns `201`. A duplicate name returns `400` `WATCHLIST_ALREADY_EXISTS`. Scope: `watchlist:management`.
PATCH /v1/config/watchlist/{watchlist_id}	Watchlist	Added; renames a watchlist and/or adds or removes symbols. Send at least one of `name`, `add_symbols`, or `remove_symbols`. Removals apply after additions, so a symbol in both lists ends up removed. Renaming to an existing name returns `400` `WATCHLIST_ALREADY_EXISTS`. Scope: `watchlist:management`.
PUT /v1/config/watchlist	Watchlist	Added; replaces the user’s entire set of watchlists with the array sent. Entries are matched by exact, case-sensitive `name`: matches are updated in place (keeping `id`), new names are created, and existing watchlists missing from the array are deleted. `[]` resets the user to a single empty `Default` watchlist. Symbols are stored as sent, without uppercasing or validation. Returns `201`; a `500` has no body. Scope: `watchlist:management`.
DELETE /v1/config/watchlist/{watchlist_id}	Watchlist	Required scope changed from `user:management` to `watchlist:management`. Response adds `invalid_symbols`, and `symbols` can now be `null`.

Release date: October 1, 2026

Market Data Error Codes, Resolution Validation, and Equity Timestamps

Company endpoints now return 404 for symbols with no data instead of an empty 200, and malformed query parameters on ETF, earnings surprise, and technical analysis endpoints now return 400 instead of 500. Technical analysis endpoints now validate resolution against a smaller set of values. Equity details timestamps are now RFC 3339.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v1/company/profile, `/company/executive`, `/company/metrics`, `/company/peers`	Company	Now return `404` `NOT_FOUND` when no data exists for the requested symbol (for `/profile`, the supplied identifiers); previously returned `200` with an empty result.
GET /v1/etf/holdings	ETF	A `skip` that is not a valid 64-bit integer now returns `400` `INVALID_PARAMETER` (was `500`).
GET /v1/stock/earnings	Stock Estimates	A `limit` that is not a valid 64-bit integer now returns `400` `INVALID_PARAMETER` (was `500`).
GET /v1/indicator	Technical Analysis	Breaking: `resolution` now accepts only `1`, `5`, `15`, `30`, `60`, `D`, `W`, and `M`; any other value, including `240` and tick resolutions such as `100T`, returns `400` `VALIDATION_ERROR`. A `from` or `to` that is not a valid 64-bit integer now returns `400` `INVALID_PARAMETER` (was `500`). Requests rejected by the data provider now return `400` `BAD_REQUEST` (was `500`).
GET /v1/scan/pattern, `/scan/support-resistance`, `/scan/technical-indicator`	Technical Analysis	Breaking: `resolution` now accepts only `1`, `5`, `15`, `30`, `60`, `D`, `W`, and `M`; any other value returns `400` `VALIDATION_ERROR`.
GET /v1/marketdata/equities/details	Market Data	`tradeTimestamp` and `quoteTimestamp` are now RFC 3339 `date-time` strings, fixing timestamps that were returned as `0`. `tradeTimestamp` is omitted when the feed timestamp is missing or invalid.

Release date: October 1, 2026

Account WebSocket Snapshot Fields

Documented the additional account and position fields returned in the account topic’s initial snapshot, and removed the legacy orders array from the snapshot contract.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
WSS `/v1/accounts/ws`	Streaming API	Breaking: the `account` subscribe snapshot no longer returns the legacy `orders` array. Use `ordersV2`.
WSS `/v1/accounts/ws`	Streaming API	`account` snapshot `account` object adds `shortSellingEnabled`, `intradayMarginBalance`, `sodMarginTradeBalance`, `sodGrossFundsAvailable`, `sodNetFundsAvailable`, `sodFundsAvailableDate` (`YYYY-MM-DD`), and `freestockUnsettleBalance`.
WSS `/v1/accounts/ws`	Streaming API	`account` snapshot `account` object now documents the already-supported `isOptionLevelEnable`, `sodTtlEquity`, and `sodTtlEquityUpdatedAt`.
WSS `/v1/accounts/ws`	Streaming API	`positions[]` in the snapshot and in `account.position` events adds `mtmRealizedPnL`, the mark-to-market realized P&L measured against the previous close.

Scope Changes and Request/Response Updates

Deprecated GET /v1/accounts/{id}/balances in favor of GET /v2/accounts/{id}/balance. Changed the required scope on Analytics, Options, and Accounts endpoints, and updated request and response contracts across Orders, OAuth2, Chart, Stocks, Options, Accounts, and other sections.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v1/accounts/{id}/balances	Accounts	Deprecated; removed from the API reference. Use `GET /v2/accounts/{id}/balance`.
GET /v1/equity/sector-tickers, `/sector-wise-change`, `/top-gainers`, `/top-losers`, `/top-most-active`	Analytics	Required scope changed from `analytics:information` to `market:information`. Added a `size` query parameter to `/sector-wise-change` (string) and to `/top-gainers`, `/top-losers`, and `/top-most-active` (integer, 1–99, default `10`).
GET /v1/options/stocks/top-gainers, `/options/stocks/top-volume`, `/options/etfs/top-volume`	Analytics	Required scope changed from `analytics:information` to `options:information`.
POST /v1/stock/screener	Analytics	Required scope changed from `analytics:information` to `market:supplemental`. The top-level `operator` is no longer required; the body must instead contain a non-empty `clauses` array or a non-empty `groups` array. Clause `field`, `operator`, and `value` are no longer marked required.
GET /v1/options/activity, `/last-trade`, `/open-close`, `/previous-day`, `/quotes`, `/trades`, `/snapshot/chain/{underlyingAsset}`, `/snapshot/{underlyingAsset}/{optionContract}`, `/{symbol}/contracts/{expiryDate}`, `/{symbol}/expiry-dates`	Options	Required scope changed from `options:information` to `market:supplemental`.
GET /v1/options/last-trade, `/trades`, `/snapshot/chain/{underlyingAsset}`, `/snapshot/{underlyingAsset}/{optionContract}`	Options	Breaking: trade `exchange` is now an `integer` (was `string`). `/snapshot/chain/{underlyingAsset}` query `expirationDate` is now `date` formatted.
GET /v1/options/unusual_activity/{symbol}	Options	Added query parameter `source` (`realtime` or `delayed`, default `delayed`).
GET /v1/stocks/last-trade, `/trades`, `/unified-snapshot`	Stocks	Breaking: trade `exchange` is now an `integer` (was `string`). `/unified-snapshot` no longer restricts `results[].type` to an enum.
GET /v1/accounts/{id}/positions	Accounts	Now accepts either `account:information` or `position:information`. Added a `503` response for when the position read model is unavailable.
GET /v2/accounts/{id}/balance	Accounts	Added a `503` response for when the balance read model is unavailable.
GET /v2/accounts/{id}/orders	Accounts	Removed the `source` query parameter.
GET /v2/users/me/accounts	Accounts	Response now declares `accounts` as required, and each account requires `trading_account_id`, `broker_account_id`, `status`, `is_sim`, `account_type`, and `account_class`. Added `STERLING_PENDING` to `status`. Removed the `400` and `404` responses.
POST /v1/orders, `/orders/preview`, `/orders/replace`, `/orders/cancel`	Orders	Added `accountId` (1–50 characters) as an alternative to `tradingAccountId`; send one of the two. `tradingAccountId` is no longer required on its own. Leg `putCall` accepts `P` and `C`, and leg `maturity` is `date` formatted. On `/orders`, `/orders/preview`, and `/orders/replace`, leg `side` accepts `B` and `S`, leg `positionEffect` accepts `O` and `C`, and `timeInForce` adds `ATO`, `ATC`, and `EXT`. On `/orders/cancel`, top-level `putCall` accepts `P` and `C`, and `maturity` is `date` formatted.
POST /v1/oauth2/token	OAuth2	Added an `application/x-www-form-urlencoded` request body alongside JSON. Added a Client Credentials grant (`grant_type=client_credentials` with `client_id` and `client_secret`). The Refresh Token grant no longer requires `client_secret`. JSON bodies take `grant_type=code` for Authorization Code and PKCE; form bodies accept `code` or `authorization_code`. String fields require at least one character. Response now requires `access_token`, `refresh_token`, `token_type` (`Bearer`), `expires_in`, `refresh_token_expires_in`, and `scope`.
GET /v1/chart/history	Chart	Added response field `nextTo`. Response `v` (volume) items are now `number` (was `integer`). Removed the `minimum: 1` constraint on `from` and `to`. `resolution` adds tick resolutions `1T`, `5T`, `10T`, `25T`, `50T`, `100T`, `250T`, `500T`, and `1000T`.
GET /v1/chart/config, `/chart/symbols`	Chart	Response fields are now declared required. `/chart/symbols` `subsessions` items now document `id` and `session`.
GET /v1/indicator	Technical Analysis	`resolution` adds the same tick resolutions as chart history. Response `sma` items are now `number` (was `integer`).
GET /v1/scan/pattern, `/scan/support-resistance`, `/scan/technical-indicator`	Technical Analysis	`resolution` adds the same tick resolutions as chart history.
GET /v1/logos/search	Logos	Breaking: `searchKeysType` values changed from `firm_id` and `firm` to `symbol`, `cik`, `cusip`, and `isin`.
GET /v1/ownership/insider-transactions	Ownership	Query `from` and `to` are now `date` formatted.
GET /v1/calendars/economics	Calendar	Response `events[].source` is no longer restricted to `cache` or `db`, and `events[].lastUpdate` is no longer `date-time` formatted.
GET /v1/calendars/mergers-acquisitions	Calendar	Response `mergersAcquisitions[].dateExpected` is no longer `date` formatted.
GET /v1/company/profile	Company	Response `exchange` is no longer restricted to an enum or given a default.
GET /v1/market/status	Market	The `400` response now uses only the nested `error` envelope (`type`, `code`, `message`, `details`, `request_id`, plus `meta`); the flat `ErrorResponse` alternative was removed.

Release date: September 28, 2026

Prediction Market Response Trimming

Prediction responses now carry only the level that was asked for. These are breaking changes to three endpoints; no endpoint was added or removed.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v1/predictions/search	Prediction Market Data	Breaking: `events` and `base-events` hits no longer carry a `contracts` array. Each hit carries its own fields and `contractsFound`, the count of matching contracts under it; list those contracts with `type=contracts` plus the hit’s `eventId` or `baseEventId`. The `contractsPerHit` parameter is removed and is now ignored rather than validated.
GET /v1/predictions/events/{eventId}/contracts	Prediction Market Data	Breaking: removed `rawPayload` from each contract. `priceLimit` and `tradingSchedule` are still passed through from the venue.
GET /v1/predictions/base-events/{baseEventId}	Prediction Market Data	Breaking: removed `rawPayload` from each contract in `data.events[].contracts`.

Release date: September 28, 2026

Prediction Market API

Added the Prediction API: five endpoints covering prediction-market historical ticks, reference data, and full-text search. The catalogue is organized as base event → event → contract, and a contract’s symbol is the key shared across every endpoint. None of these routes requires an API key or bearer token. Each endpoint offers a server dropdown for https://api.aries.com (production) and https://api.tradearies.dev (staging); this selector applies to the prediction endpoints only. No existing endpoint changed.These replace the prediction-market endpoints documented before May 2026, which used the retired product / instrument vocabulary: GET /v1/predictions/events/\{eventId\}/instruments and GET /v1/predictions/products/\{productId\} are gone and now return 404.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v1/predictions/historical-data	Prediction Historical Data	Added; returns YES/NO tick history for one `symbol`. Optional `from`/`to` accept RFC3339 or Unix seconds/milliseconds and are both inclusive; omit both for the service default window. `limit` of `0` or omitted means 10,000 and larger values are clamped to it, so the response never reports a limit larger than the one applied. `yesPrice`, `noPrice` are exact decimals serialized as JSON strings. Errors: `400`, `502`.
POST /v1/predictions/historical-data/batch	Prediction Historical Data	Added; takes `queries`, 1–5 entries, each with its own `symbol` and optional `from`/`to`/`limit`. `data.results` holds one result per query in request order; a symbol with no ticks in its window returns `count: 0` and an empty `ticks` array rather than being dropped. Errors: `400` (malformed JSON, empty `queries`, more than 5, or a query missing `symbol`), `502`.
GET /v1/predictions/search	Prediction Market Data	Added; full-text search over one index of event contracts. `type` (`contracts` default, `events`, `base-events`) picks the hit shape and is echoed in `data.type`. Filters (`state`, `baseEventId`, `eventId`, `tradable`) always apply at the contract level, so with `type=events` or `base-events` a hit is found only through its matching contracts — one with none is not returned. `state` defaults to `ACTIVE`; `*` matches every state including `DELETED`. `perPage` defaults to 20, clamped to 100; `contractsPerHit` defaults to 3, clamped to 99, ignored for `contracts`. Omit `q` to browse by soonest last-trade date. The index trails the catalogue by seconds. Errors: `400`, `502`.
GET /v1/predictions/events/{eventId}/contracts	Prediction Market Data	Added; returns one event plus every contract under it, read live from the catalogue. This is the endpoint to read `state` and `tradable` from — a search hit’s copies may be seconds stale. `tickSize` is a decimal string. `expectedPayoutTime`, `expectedLastTradeTime`, `expectedResolutionTime` are venue wall-clock times with no zone, so the trailing `Z` is a label, not a conversion. Errors: `400`, `404`, `500`.
GET /v1/predictions/base-events/{baseEventId}	Prediction Market Data	Added; returns a base event with its events and each event’s contracts as one nested tree (`data.baseEvent`, `data.events[].event`, `data.events[].contracts`). Errors: `400`, `404`, `500`.

Release date: September 27, 2026

Account Balance v2 Withdrawable Cash and Margin Fields

Added six response fields to the Account Balance (v2) endpoint covering withdrawable cash and the intraday margin balance. No existing field changed.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v2/accounts/{id}/balance	Accounts	Added `fundsAvailableForWithdrawal` (cash available to withdraw now; derived from the lower of `creditRemaining` and `smaCreditRemaining` plus the previous-close haircut, floored at zero), `intradayMarginBalance` (margin loan outstanding, rolled forward through today’s trading), and the start-of-day inputs `sodMarginTradeBalance`, `sodGrossFundsAvailable`, `sodNetFundsAvailable` (each `"0"` until the day’s load has run) and `sodFundsAvailableDate` (business date of that load; omitted when it has never run for the account). All amounts are decimal strings. Example updated to match.

Release date: September 17, 2026

Easy-to-Borrow Endpoints

Added two endpoints exposing today’s easy-to-borrow (ETB) list — the complete set of US equities that can be sold short without first locating shares. Membership in the list is the whole signal: a symbol on the list is easy to borrow, and a symbol absent from it is hard to borrow. Neither endpoint is account-scoped. No existing endpoint changed.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v1/etb	Market Data	Added; returns the whole easy-to-borrow list as `symbols` (uppercase, sorted ascending, no duplicates, never `null`) and `count`. Takes no parameters and no account ID. The list is replaced once per trading day before market open and does not change intraday; a failed update leaves the previous day’s list in place. `{"symbols": [], "count": 0}` is a valid `200` meaning the list has not loaded yet — not that nothing is borrowable. No caching headers are set.
POST /v1/etb/search	Market Data	Added; takes `symbols` (1–1000 entries, case-insensitive, whitespace-trimmed) and returns `results`, a map of normalized uppercase symbol to boolean, plus `count`. Duplicates collapse after normalization, so `count` can be lower than the number of symbols sent — read answers by uppercase key, not by index. Errors use the nested `error` envelope: `400 MISSING_BODY`, `400 INVALID_BODY` (malformed JSON or body over 1 MiB), `400 MISSING_SYMBOLS`, `400 TOO_MANY_SYMBOLS` (over 1000), `500 INTERNAL_ERROR`. There is no `404` — a symbol absent from the list is a valid `false`.

Release date: August 25, 2026

Economics and Earnings Calendar Updates

Added support for date-range queries on the Economics Calendar endpoint, and new time and importance fields on the Earnings Calendar endpoint.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v1/calendars/economics	Calendar	Added query parameters `from` and `to` for date-range filtering (e.g., `?from=2024-01-15&to=2024-03-15`). The `date` parameter (e.g., `?date=2024-01-15`) still supported — returns events for that date plus 1 month lookahead. Choose one mode per request; both return the same response structure.
GET /v1/calendars/earnings	Calendar	Added `time` field (24-hour format, e.g., `16:39:00`) giving the exact release time, and `importance` field (integer 1-3, where 3 is most important) to prioritize high-impact earnings releases.

Tick-Based Chart Data Endpoint

Added a new endpoint for tick-based chart bars — candles that close every N trades instead of every N minutes, useful for visualizing market activity on fast-moving symbols. Historical Bars no longer accepts tick resolutions; it previously served them silently as 1-minute bars.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v1/chart/tick-history	Chart	Added; returns tick-based OHLCV bars for resolutions `1T, 5T, 10T, 25T, 50T, 100T, 250T, 500T, 1000T`. Supports `symbol`, `resolution`, `countback` (default 300; maximum depends on resolution — up to 5000 bars for low-count ticks like `1T`, as few as ~50 for `1000T`, since each call is bounded by a fixed per-request trade budget), and `cursor` (opaque pagination token for loading older history). Response includes `nextTo`, an opaque cursor to pass back for the next older page; absent when no more history is available. Bar timestamps (`t`) are Unix milliseconds, always strictly increasing.
GET /v1/chart/history	Chart	Tick resolutions (`1T`–`1000T`) are no longer accepted on this endpoint and now return an error; use `GET /v1/chart/tick-history` instead. Previously these resolutions were silently served as 1-minute bars.

Release date: July 27, 2026

Market Data WebSocket Fundamental Quote Fields

Documented fundamental and reference fields that the market data WebSocket accepts in quoteFields and returns from the symbol snapshot. These were already supported by the backend but previously undocumented.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
WSS `/v1/market/ws`	Streaming API	Documented additional `quoteFields` values: `type`, `sicCode`, `hasOptions`, `sharesOutstanding`, `assets`, `liabilities`, `longTermDebt`, `EPSDiluted`, `EPSLatest12Month`, `EPS3YearGrowthRate`, `EPS5YearGrowthRate`, `avgVolume4Weeks`, `PE`, `high52WeekPrice`, `high52WeekDate`, `low52WeekPrice`, `low52WeekDate`, `dividend`, and `shortSaleRestricted`. Values are delivered as strings (except `hasOptions`, a boolean); field names are case-sensitive.

Account Balance v2 and Positions Fields

Documented additional response fields now returned by the Account Balance (v2) and Account Positions endpoints.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v2/accounts/{id}/balance	Accounts	Added response fields `openPnl`, `dayOpenPnl`, `dayRealizedPnl`, `dayTotalPnl`, `costOfPositions`, `cashBalance`, `amountAvailableToWithdraw`, and `sodTtlEquityUpdatedAt`. Example updated to match.
GET /v1/accounts/{id}/positions	Accounts	Added response fields `positions.price`, `positions.marketValue`, and `positions.costBasis` (omitted for closed positions). Example updated to match.

Account Positions and Balance v2

Removed the availability block from the Account Positions response and added a v2 Account Balance endpoint.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v1/accounts/{id}/positions	Accounts	Removed the `availability` object (`available`, `source`) from the response; positions are now returned without data-availability metadata.
GET /v2/accounts/{id}/balance	Accounts	Added v2 account balance endpoint returning a flat balance object. Same fields as v1 balances plus `balance` and `smaCreditRemaining`; does not include `totalEquity` or `sodTtlEquityUpdatedAt`.

Streaming API Watchlist Merge Alignment

Updated the Streaming API documentation to match the backend account WebSocket contract. Watchlist streaming is now documented only under the account WebSocket, and the watchlist request and response examples now reflect the backend’s full-watchlist snapshot and full-watchlist event payloads.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
WSS `/v1/accounts/ws`	Streaming API	Watchlist documentation moved under Account Updates WebSocket; removed the separate Watchlist WebSocket page from navigation
WSS `/v1/accounts/ws`	Streaming API	`watchlist` subscribe response now documents the current watchlist array returned immediately after subscribe
WSS `/v1/accounts/ws`	Streaming API	`watchlist` event payload now documents the full watchlist array returned on each update
WSS `/v1/accounts/ws`	Streaming API	News subscription docs now document symbol filtering only

Account Positions P&L Fields

Aligned the Account Positions response P&L fields with the live API.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v1/accounts/{id}/positions	Accounts	Added response field `positions.todayPl`; removed `positions.dailyPl` (no longer returned). Examples updated accordingly.

Single-Ticker Query Parameter Rename

Renamed the single-symbol query parameter from tickers to ticker on six endpoints. The multi-symbol parameter tickersAnyOf is unchanged. This is a breaking change for callers that sent ?tickers=AAPL — switch to ?ticker=AAPL.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET `/v1/financials/short-volume`	Financials	Query parameter `tickers` renamed to `ticker` (single symbol only); `tickersAnyOf` unchanged
GET `/v1/financials/ratios`	Financials	Query parameter `tickers` renamed to `ticker` (single symbol only); `tickersAnyOf` unchanged
GET `/v1/financials/short-interest`	Financials	Query parameter `tickers` renamed to `ticker` (single symbol only); `tickersAnyOf` unchanged
GET `/v1/corporate-actions/dividends`	Corporate Actions	Query parameter `tickers` renamed to `ticker` (single symbol only); `tickersAnyOf` unchanged
GET `/v1/stock/split`	Corporate Actions	Query parameter `tickers` renamed to `ticker` (single symbol only); `tickersAnyOf` unchanged
GET `/v1/stocks/unified-snapshot`	Stocks	Query parameter `tickers` renamed to `ticker` (single symbol only); `tickersAnyOf` unchanged
GET /v1/accounts/{id}/positions	Accounts	Response `positions.securityType` enum corrected from `[CS, OPT]` to `[EQUITY, OPTION]`; examples updated to `EQUITY`; description clarified. Orders endpoints (which use `[CS, OPT]`) are unchanged.
GET /v1/chart/symbols	Chart	Documented seven previously-missing response fields on `SymbolInfo`: `subsession_id`, `subsessions` (nullable array), `has_daily`, `has_ticks`, `daily_multipliers`, `weekly_multipliers`, `monthly_multipliers`. Example payload updated to match the current API response.

Account Positions Availability Source

Corrected the availability.source response field for the Account Positions endpoint to match the live API.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v1/accounts/{id}/positions	Accounts	Response `availability.source` enum value `db` corrected to `database` (now `[cache, database]`); description updated to “Where the positions data was read from”. Orders endpoints are unchanged.

Calendar and Options Request Contract Updates

Documentation updated for current public request-contract changes reflected in the backend.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET `/v1/calendars/historical/{symbol}`	Calendar	Blank, whitespace-only, and placeholder path values such as `{symbol}` are rejected with `400 Bad Request`
GET `/v1/stocks/unified-snapshot`	Stocks	Added docs guidance explaining that in the playground, entering `tickers` and then selecting `type` can clear the `tickers` field

Sort Parameter Input Alignment

Corrected sort parameter documentation across the API reference so Mintlify renders text inputs for sort instead of enum/default selectors.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET `/v1/stock/split` and `/v1/corporate-actions/dividends`	Corporate Actions	`sort` now renders as a text input and documents provider-style sort expressions such as `execution_date.desc` and `ticker.asc`
GET `/v1/economy/inflation`, `/inflation-expectations`, `/treasury-yields`	Economy	`sort` now renders as a text input instead of an enum/default selector
GET `/v1/financials/short-volume`, `/ratios`, `/short-interest`, `/cash-flow-statements`, `/income-statements`	Financials	`sort` now renders as a text input instead of an enum/default selector
GET `/v1/stocks/aggs`, `/unified-snapshot`, `/trades`, `/quotes`	Stocks	`sort` now renders as a text input instead of an enum/default selector
GET `/v1/options/snapshot/chain/{underlyingAsset}`, `/trades`, `/quotes`	Options	`sort` now renders as a text input instead of an enum/default selector

Orders, Watchlist, Indices, and Options Changes

Request and response field changes across Orders, Watchlist, Indices, and Options endpoints.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
POST /v1/orders, `/orders/cancel`, `/orders/replace`	Orders	Request `symbol` maxLength increased from `20` to `21`. Same change on `OrdLeg.symbol`.
POST /v1/orders/cancel	Orders	Request `side` is now required (previously optional).
POST /v1/orders/replace	Orders	Added request fields: `currency` (3-letter ISO code) and `legs` (array of `OrdLeg`, max 4).
DELETE /v1/config/watchlist/{watchlist_id}	Watchlist	Added; deletes the watchlist or, when it is the user’s last one, resets it to a `Default` empty watchlist. Returns the affected watchlist (`{ id, name, symbols }`)
GET /v1/indices/bars	Indices	`precision` enum value `Days` removed (now `[Minutes, Hours]`).
GET /v1/indices/bar, `/bars`, `/chart-bars`, `/realtime/values`	Indices	`identifierType` now accepts an additional value `CIK` (8 values total: `Symbol`, `CIK`, `CUSIP`, `ISIN`, `Valoren`, `SEDOL`, `FIGI`, `CompositeFIGI`).
GET /v1/options/previous-day	Options	Response schema now declares `required: [ticker, open, high, low, close, volume]`; `volumeWeighted`, `timestamp`, `transactionCount` remain optional.
GET /v1/equity/sector-wise-change	Analytics	`limit` parameter type changed from `integer` to `string` so the literal value `all` can be sent alongside numeric values.

Market Exchange Codes and v2 Orders Schema Alignment

Documented supported market exchange query values and aligned v2 orders schemas and companion pages with the trading API.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v1/market/status	Market	`exchange` query uses the `ExchangeCode` enum (79 codes); default `US`; supported list on reference page
GET /v1/market/holiday	Market	Same `exchange` enum and supported exchange documentation as market status
GET /v2/accounts/{id}/orders	Accounts	Documented `GetOrdersV2Response` required fields; `TradeOrderV2` required properties and FIX enums; flat `ErrorResponse` 400 for invalid `source`
GET /v2/accounts/{id}/orders/history	Accounts	Same response schema alignment; documented flat 400 examples (`from is required`, invalid timestamps, `order_by`, 90-day cap)

API Response Documentation Fixes

Corrected documented response schemas and examples to match current API payloads.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v1/etf/sector	ETF	200 response examples now document `industry` on each `sectorExposure` entry instead of stale `sector`
GET /v1/stock/split	Corporate Actions	200 response now documents `{ results, status }`; each split event uses `ticker`, `executionDate`, `splitFrom`, and `splitTo` with optional pagination metadata
GET /v1/stock/transcripts/list	Stock Alternative	200 response now documents `{ symbol, transcripts }`; each transcript entry includes `id`, `quarter`, `time`, `title`, and `year`
GET /v1/indices/list	Indices	200 response entries now document `indexName`, `symbol`, `indexGroup`, and `currency`; removed stale `name`, `description`, `exchange`, and `valoren` fields
GET /v1/indices/by-group	Indices	200 response now documents `valoren` on each `indices` entry

v2 Orders API Documentation Updates

Added v2 account orders endpoint documentation and clarified request/response contracts for active and historical order retrieval.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
`GET /v2/accounts/{id}/orders`	Accounts	Added endpoint documentation for paginated active orders; response documented as v2 domain order objects with `{ orders, nextCursor }`
`GET /v2/accounts/{id}/orders/history`	Accounts	Added endpoint documentation for date-range order history; documented required `from`, optional `to`, cursor pagination, `order_by`, and `exclude_today` behavior with same v2 response shape

API Request/Response Documentation Fixes

Documentation was updated to match current backend query validation, public endpoint auth behavior, and response shapes.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
wss://api.aries.com/v1/market/ws	Streaming API	Moved WebSocket authentication to the first-class auth message and operation position in the AsyncAPI spec
GET /v1/analytics/market-breadth	Analytics	200 response now documents `{ success, data }`; timestamp wording allows fractional seconds
GET /v1/analytics/net-inflow	Analytics	200 response now documents `{ success, data }`; timestamp wording allows fractional seconds
GET /v1/chart/history	Chart	Removed lowercase resolution enum variants; documented uppercase `D`, `W`, `M`, `1D`, `1W`, `1M`, `3M`, `6M`, and `12M` values
GET /v1/equity/top-gainers, `/top-losers`, `/top-most-active`, `/sector-tickers`	Analytics	`SymbolDetails` examples and schema no longer document `description` or `tag`
GET /v1/options/stocks/top-gainers, `/stocks/top-volume`, `/etfs/top-volume`	Options	Documented option `type` response codes as `c` for Call and `P` for Put
GET /v1/options/unusual_activity/	Options	Documented optional `next_page` pagination pointer in the response
GET /v1/options/snapshot/chain/ and `/snapshot/{underlyingAsset}/{optionContract}`	Options	Removed provider-specific response wording from request/status/Greeks descriptions
GET /v1/financials/ratios	Financials	Added `tickersAnyOf`; `tickers` now documented as single-symbol only; documented 400 rules for multi-value `tickers` and `tickers`+`tickersAnyOf` conflict
GET /v1/financials/short-interest	Financials	Added `tickersAnyOf`; `tickers` now documented as single-symbol only; documented same two 400 validation rules
GET /v1/financials/short-volume	Financials	Added `tickersAnyOf`; `tickers` now documented as single-symbol only; documented same two 400 validation rules
GET /v1/financials/cash-flow-statements	Financials	Removed provider-specific wording from `tickers`, `sort`, and `next` parameter descriptions
GET /v1/financials/income-statements	Financials	Removed provider-specific wording from `tickers`, `sort`, and `next` parameter descriptions
GET /v1/corporate-actions/dividends	Corporate Actions	Query contract aligned: removed legacy `ticker`, documented `tickers` (single symbol) + `tickersAnyOf` (multi-symbol) and 400 conflict rules
GET /v1/stock/split	Corporate Actions	Query contract aligned: removed legacy `ticker`, documented `tickers` (single symbol) + `tickersAnyOf` (multi-symbol) and 400 conflict rules
GET /v1/stocks/unified-snapshot	Stocks	Added `tickersAnyOf`; `tickers` documented as single-symbol only; documented 400 conflict rules; options payload field descriptions aligned to backend optional fields
GET /v1/financials/reported	Financials	Corrected request contract: at least one of `symbol`, `cik`, or `accessNumber` is required; `freq`, `from`, `to` remain optional
GET /v1/financials/revenue-breakdown	Financials	Corrected request contract: at least one of `symbol` or `cik` is required (both are no longer documented as required together)
GET /v1/filings/similarity-index	Filings	Clarified that either `symbol` or `cik` must be provided, while `freq` remains optional
GET /v1/calendars/mergers-acquisitions	Calendar	Updated the response example to include current acquisition fields such as `dateExpected`, acquirer details, and `notes`
`DataAvailability` schema	Accounts	`available` and `source` are no longer documented as required fields

API Request/Response Documentation Updates

Request and response docs were updated to align endpoint contracts with live API behavior.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v1/company/metrics	Company	Query `metric` documentation now supports `all` only; removed other documented enum values
GET /v1/company/executive	Company	200 response schema updated to `executives[]` with fields `age`, `compensation`, `currency`, `name`, `position`, `sex`, `since`
GET /v1/company/profile	Company	Request docs clarified that at least one of `symbol`, `isin`, or `cusip` is required; omitting all returns 400
GET /v1/marketdata/equities/details	Market Data	200 response docs aligned to current live payload shape (`data` + `errors` and field mapping)
GET /v1/accounts//positions	Accounts	200 response fields aligned to live payload naming and structure

API Request/Response Updates

Request and response docs were aligned to live API payloads across Accounts, Financials, Market Data, Orders, and Options. This update also adds the new option snapshot endpoints and broadens documented error response coverage.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v1/users/me/accounts	Users	200 response now documents `account_type` and `account_class` on account objects
GET /v1/accounts//balances	Accounts	200 response aligned to the flat top-level balance payload with all returned fields and decimal-string amounts
GET /v1/accounts//positions	Accounts	200 response aligned to `{ positions, availability }` with decimal-string numeric fields
GET /v1/marketdata/equities/details	Market Data	Response wrapper clarified as `data` plus `errors`; field names now reflect service JSON output
GET /v1/marketdata/search	Market Data	200 response clarified as a top-level JSON array, not a `results` wrapper
POST /v1/orders/preview	Orders	Preview response now includes `warnRuleId` in the documented equity and option preview payloads
GET /v1/options/snapshot/chain/	Options	New endpoint added; request supports option chain filters and the response returns paginated snapshot data with `requestId`, `status`, `results`, and `nextUrl`
GET /v1/options/snapshot//	Options	New endpoint added; response returns contract metadata, day bar, last quote, last trade, Greeks, and underlying snapshot data
Multiple endpoints	Cross-API	Added and standardized missing `400`, `401`, `403`, `404`, and `500` error responses to better match live API behavior

Updated on: April 13, 2026

API Documentation Updates

Critical endpoint corrections and response schema updates to align documentation with the API.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v1/analytics/insights	Analytics	Fixed endpoint path typo: `/v1/analyst/insights` → `/v1/analytics/insights` (breaking)
GET /v1/stock/dividend2	Corporate Actions	Deprecated - Endpoint removed completely from API and documentation
GET /v1/news	News	Request params changed to `symbols`, `topics`; response changed from `articles` to `news` array (breaking)
GET /v1/news/	News	Added new endpoint to retrieve single news item by ID with `newsType` query param
GET /v1/company/profile	Company	Added 404/500 error responses; updated response example with all fields including masked logo URL
GET /v1/users/me	Users	Added response fields: `avatar_url`, `email_verified`, `primary_phone_number`

Breaking Changes:

/v1/analyst/insights → /v1/analytics/insights (path correction)
/v1/stock/dividend2 removed (use /v1/corporate-actions/dividends)
/v1/news response: articles → news array

Release date: February 16, 2026

API & Documentation

API and documentation updates: response renames for stock estimates and earnings, Fundamentals and Watchlist schema changes, Analytics ratings and equity details, order and OAuth schema changes, and WebSocket docs and endpoints.Summary of changes by endpoint:

Endpoint	Section	Change (short & precise)
GET /v1/stock/revenue-estimate	Stock Estimates	Response root key renamed: `data` → `revenueEstimates` (breaking)
GET /v1/stock/ebitda-estimate	Stock Estimates	Response root key renamed: `data` → `ebitdaEstimates` (breaking)
GET /v1/stock/ebit-estimate	Stock Estimates	Response root key renamed: `data` → `ebitEstimates` (breaking)
GET /v1/stock/eps-estimate	Stock Estimates	Response root key renamed: `data` → `epsEstimates` (breaking)
GET /v1/stock/earnings	Earnings	Response root key renamed: `data` → `earningSurprises` (breaking)
GET /v1/financials/reported	Fundamentals	Added `accessNumber`, `freq`; `from`/`to` now use `date` format
GET /v1/financials/revenue-breakdown	Fundamentals	Removed `from` and `to`; only `symbol` and `cik` remain
GET /v1/financials/statements	Fundamentals	Required: `symbol`, `statement`, `freq`; optional: `preliminary`; removed `from`, `to`
POST /v1/watchlist	Watchlist	`account_id` replaced by `user_id` (integer)
PUT /v1/watchlist	Watchlist	Request/response updated to use `user_id`
GET /v1/watchlist	Watchlist	Response requires `user_id` and `watchlist`; symbols minItems removed
GET /v1/analytics/ratings	Analytics – Ratings	Added query params: `action`, `analystId`, `firmId`
GET /v1/analytics/ratings	Analytics – Ratings	Pagination defaults/max removed; `importance` min/max removed
GET /v1/analytics/ratings	Analytics – Ratings	Schemas switched to `snake_case`; new Rating & Accuracy fields added
GET /v1/analytics/ratings	Analytics – Ratings	`GetRatingsResponse` now requires `ratings`
GET /v1/marketdata/equities/details	Market Data	Response now requires `data` and `errors`; equity fields expanded
GET /v1/marketdata/search	Market Data	Added futures search example (`query: "/ES"`)
POST /v1/orders	Orders	`timeInForce` enum extended
POST /v1/orders	Orders	`exDestination` removed from request schema
POST /v1/orders/preview	Orders	`cost` renamed to `estimatedCost`; added `estimatedMargin`
POST /v1/orders/preview	Orders	Removed reject/warn fields; added `warnings` and `errors` arrays
POST /v1/oauth2/authorize	OAuth2	OAuth paths standardized under `/v1/oauth2/`
POST /v1/oauth2/authorize	OAuth2	New encrypted password example; `response_type` enum = `code`
POST /v1/oauth2/authorize/confirm	OAuth2	Examples include `is_mfa` and `consent_required`
POST /v1/oauth2/authorize/mfa	OAuth2	`is_mfa` appears only on MFA authorize responses
wss://api.aries.com/v1/market/ws	WebSockets	Market Data WebSocket endpoint renamed
wss://api.aries.com/v1/charts/ws	WebSockets	New Charting WebSocket endpoint
/v1/charts/ws	WebSockets	Docs expanded; “Under Development” warning removed

For stock estimate endpoints, the array remains under *.data; symbol and freq stay in the same wrapper. For earnings, the root value is the array: { "earningSurprises": [ ... ] }. Docs and API use /v1/oauth2/... (not /oauth/...).Release date: February 6, 2025

Documentation

Added official SDK documentation for Python, Go, and JavaScript. Each SDK includes installation instructions, authentication setup, and complete API references.What’s included:

Quick Start Guides - Get started with code examples for placing orders, checking balances, and retrieving market data
Authentication - OAuth2 flows with PKCE, MFA support, and automatic token refresh
API References - Full documentation for 9 endpoints: Accounts, Orders, Users, Analytics, Market Data, Watchlist, Chart, News & Calendars, and Settings
Code Examples - 30+ examples covering market orders, limit orders, stop losses, bracket strategies, and portfolio management
Error Handling - Common error patterns and how to handle them in each language
TypeScript Support - Full type definitions for JavaScript/TypeScript users

All three SDKs provide the same functionality with language-specific conventions and idioms.Release date: December 16, 2025

Documentation

Complete documentation overhaul for Fundamentals API with enhanced schemas and real-world examples to streamline integration.Enhanced Documentation Coverage:

All 18 Fundamentals API endpoints now include comprehensive request/response examples
Added detailed field descriptions for company metrics, financials, and ownership data
Included common use cases and filtering patterns for faster implementation

This documentation update makes it significantly easier to integrate company data, financials, and ownership information into trading applications.Release date: December 12, 2025

API Feature Releases

Added WebSocket streaming APIs and supplemental REST endpoints.New WebSocket connections:

Market Data WebSocket for quotes, trades, and Level 2 orderbook data across equities, indices, and options
TradingView Chart WebSocket for real-time chart data
Account Updates WebSocket for order, position, balance, and P&L updates
Watchlist WebSocket for live watchlist synchronization

New supplemental endpoints:

Market movers: GET /v1/equity/top-gainers, GET /v1/equity/top-losers, GET /v1/equity/top-most-active
Sector analysis: GET /v1/equity/sector-tickers, GET /v1/equity/sector-wise-change
Options flow: GET /v1/options/stocks/top-volume, GET /v1/options/etfs/top-volume
Market indicators: GET /v1/analytics/market-breadth, GET /v1/analytics/net-inflow
Calendar, company, ownership, financials, filings, IPO, and dividend endpoints

Release date: December 11, 2025

New Feature

Enhanced market intelligence with calendar events, detailed equity information, and advanced analytics for systematic trading strategies.Calendar Integration:

GET /v1/calendars/economics - Track economic events that impact market volatility
GET /v1/calendars/earnings - Monitor upcoming earnings with symbol and date filtering
GET /v1/calendars/historical/{symbol} - Access historical indicator data for backtesting

Enhanced Market Data:

GET /v1/marketdata/equities/details - Batch retrieve detailed equity information for up to 50 symbols in a single request, reducing API calls and improving performance

Analytics Suite:

Analyst ratings with filtering by ticker, date range, and importance level
Real-time market breadth showing advancers vs. decliners across exchanges
Net inflow data for NASDAQ and NYSE to track institutional money flow

These endpoints provide the data foundation for building algorithmic trading strategies and market surveillance tools.Release date: October 27, 2025

New Feature

Initial release of Aries API with OAuth2 authentication, order execution, and account management capabilities for building trading applications.Release date: August 5, 2025

​Recent Updates

Recent Updates