Skip to main content

Changelog

2026-04-20​

base and quote fields omitted when empty in index reference data endpoints​

The base and quote fields are now omitted from the JSON response when their values are empty, for the following endpoints:

  • GET /api/v1/indices — list of index summaries
  • GET /api/v1/indices/{externalId} — single index summary
  • GET /api/v1/indices/{externalId}/detail — index detailed

Previously, these fields were always present (potentially as empty strings). They are now nullable and excluded from the response when the index has no base or quote asset configured.

As a result, the following index types no longer populate base and quote:

  • Reward Rate (e.g. APT_SRR)

maxResolution field added to index reference data endpoints​

Added maxResolution: string to the response of the following endpoints:

  • GET /api/v1/indices — list of index summaries
  • GET /api/v1/indices/{externalId} — single index summary
  • GET /api/v1/indices/{externalId}/detail — index detailed

The field indicates the maximum publication frequency for the index (e.g. "PER_SECOND", "PER_200MS", "DAILY").

Subsecond resolution support for REST and WebSocket APIs​

Added optional maxResolution parameter to REST endpoints and WebSocket subscriptions.

REST endpoints affected: /api/v1/values, /api/v1/latest_values, /api/v1/summary, /api/v1/summaries

  • maxResolution=PER_SECOND (default): returns only values at second boundaries (unchanged behaviour for all existing clients)
  • maxResolution=PER_200MS: returns all ticks, including those between second boundaries
  • Any other value returns HTTP 400 Bad Request

WebSocket value channel subscribe message:

  • maxResolution: "PER_SECOND" (default): stream delivers only second-boundary ticks
  • maxResolution: "PER_200MS": stream delivers all ticks at their original timestamps; accepted for all indexes and has no additional effect on indexes that do not publish at 200ms frequency

WebSocket Info response: isSubSecond replaced by maxResolution​

The streams array in the info response no longer contains an isSubSecond boolean field. It is replaced by a maxResolution string field that reflects the index's maximum publication frequency (e.g. "PER_SECOND", "PER_200MS", "DAILY"), consistent with the REST refdata endpoints.

2026-04-06​

active_corporate_action added to api​

Added a new active_corporate_action stream type for REST and WebSocket APIs, available for xStocks rti indices.

  • REST: GET /api/v1/stats?id=<index>&streamtype=activecorporateaction
  • WebSocket: subscribe with "stream": "active_corporate_action"

API Documentation Update​

Added changelog to API documentation.