True Markets TrueX Websocket API 1.0.0

Overview

This API allows clients to interact with the TrueX trading platform for real time instrument, market data and exchange transactions.

Authentication

Certain API requests must be authenticated using HMAC-SHA256 signature authentication.

Servers

  • wss://uat.truex.co/wssuat

    TrueX UAT websocket sandbox server.

    Security:
    • HTTP API key
      • Name: x-no-auth
      • In: query

      Clients may subscribe to endpoints without an API key or computing an HMAC signature. These endpoints are rate limited by the server, coalescing and only sending data at a predetermined rate. Non-authenticated connections can be upgraded by supplying an API key and computed HMAC signature on the the next request sent to the server.

      Unauthenticated requests must be have the type: SUBSCRIBE_NO_AUTH and not include the follow fields on the requet: organization_id, key, signature.

      Required members

      • timestamp: A UTC Unix epoch in seconds.
    • HTTP API key
      • Name: x-api-key
      • In: query

      Clients must compute and send an HMAC signature in signature member of the request structure. The HMAC signature gets applied to the following payload:

      timestamp + TRUEXWS + key + path

      Note, path is everything after the domain name including the / (e.g. /api/v1).

      Required members

      • signature: The signature generated from processing the payload with the HMAC key.
      • key: The ID of the HMAC key being used.
      • timestamp: A UTC Unix epoch in seconds.
  • wss://prod.truex.co/wssproduction

    TrueX production websocket server.

    Security:
    • HTTP API key
      • Name: x-no-auth
      • In: query

      Clients may subscribe to endpoints without an API key or computing an HMAC signature. These endpoints are rate limited by the server, coalescing and only sending data at a predetermined rate. Non-authenticated connections can be upgraded by supplying an API key and computed HMAC signature on the the next request sent to the server.

      Unauthenticated requests must be have the type: SUBSCRIBE_NO_AUTH and not include the follow fields on the requet: organization_id, key, signature.

      Required members

      • timestamp: A UTC Unix epoch in seconds.
    • HTTP API key
      • Name: x-api-key
      • In: query

      Clients must compute and send an HMAC signature in signature member of the request structure. The HMAC signature gets applied to the following payload:

      timestamp + TRUEXWS + key + path

      Note, path is everything after the domain name including the / (e.g. /api/v1).

      Required members

      • signature: The signature generated from processing the payload with the HMAC key.
      • key: The ID of the HMAC key being used.
      • timestamp: A UTC Unix epoch in seconds.

Operations

  • SEND /api/v1

    Message sent to server indicating what channels and data the user would like to subscribe to.

    Operation IDsubscribeToChannel

    Available only on servers:

    Accepts the following message:

    Message IDsubscription
    object

    Examples

  • RECEIVE /api/v1

    Message received when connecting to the server and establishing a websocket connection.

    Operation IDwelcomeFromServer

    Available only on servers:

    Accepts the following message:

    Message IDwelcome
    object

    Examples

  • RECEIVE /api/v1

    Message sent from server containing channels and items the user is currently subscribed to.

    Operation IDconfirmationFromServer

    Available only on servers:

    Accepts the following message:

    Message IDconfirmation
    object

    Examples

  • RECEIVE /api/v1

    Message sent from server with instrument data.

    Operation IDinstrumentFromServer

    Available only on servers:

    Accepts the following message:

    Message IDinstrument
    object

    Examples

  • RECEIVE /api/v1

    Message sent from server containing the lasted trade information for a subscribed instrument.

    Operation IDtradeFromServer

    Available only on servers:

    Accepts the following message:

    Message IDtrade
    object

    Examples

  • RECEIVE /api/v1

    Message sent from server containing the lasted exchange best bid and offer information for a subscribed instrument.

    Operation IDebboFromServer

    Available only on servers:

    Accepts the following message:

    Message IDebbo
    object

    Examples

Messages

  • #1
    Message IDsubscription
    object
  • #2
    Message IDwelcome
    object
  • #3
    Message IDconfirmation
    object
  • #4
    Message IDinstrument
    object
  • #5
    Message IDtrade
    object
  • #6
    Message IDebbo
    object

Schemas

  • object
  • object
  • object
  • object
  • object