Skip to main content

Index Data

The index price of different assets to be subscribed are controlled by the parameters in the subscription message listed below.

/trading-api/v1/index-data

Operations

SEND/trading-api/v1/index-data

Subscribe

Multiple subscriptions could be opened within the same websocket.

The index price of different assets to be subscribed are controlled by the parameters in the subscription message listed below.

Operation IDsubscribe

Accepts the following message:

Subscription

Let you subscribe to a given topic

  • application/json
Message IDsubscribe
object

Examples

RECEIVE/trading-api/v1/index-data

After subscribing, the server sends :

  • an acknowledgement
  • followed by incremental updates.
Operation IDsubscribe-ack

Sends one of the following messages:

  • #1Acknowledgment

    Confirm the topic being subscribed

    • application/json
    Message IDsubscribe-ack
    object

    Examples

  • #2Update

    Incremental update to the subscribed index data

    • application/json
    Message IDsubscribe-msg-0
    object

    Examples

RECEIVE/trading-api/v1/index-data

In case of invalid subscription message, an error rejection would be sent.

Operation IDsubscribe-nack

Sends the following message:

Rejection

Explain why the topic could not be subscribed

  • application/json
Message IDsubscribe-nack
object

Examples

SEND/trading-api/v1/index-data

Keepalive

In case nothing is subscribed to, keep the websocket connection alive.

Operation IDkeepalive-ping

Accepts the following message:

Keepalive Ping
  • application/json
Message IDkeepalive-ping
object

Examples

RECEIVE/trading-api/v1/index-data

Acknowledgement returned by the server in response to a keepalive-ping.

Operation IDkeepalive-pong

Sends the following message:

Keepalive Pong
  • application/json
Message IDkeepalive-pong
object

Examples