Package velox.api.layer1.data

Class InstrumentInfo

java.lang.Object
velox.api.layer1.data.InstrumentCoreInfo
velox.api.layer1.data.InstrumentInfo
All Implemented Interfaces:
Serializable
Direct Known Subclasses:
InstrumentInfoCrypto
public class InstrumentInfo extends InstrumentCoreInfo implements Serializable
Information about the instrument
See Also:

  • Field Details

    • pips

      public final double pips
      Also known as min tick, tick size or minimal price increment. This allows bookmap to translate level numbers to price that is shown to the user and vice versa

    • multiplier

      public final double multiplier
      Similar to "tick value" in its meaning, with the only difference of being per price unit instead of per tick (can be computed as tick value divided by pips)

      Specifically, this field tells bookmap the following: "how many dollars (or other currency units) will my P&L change if I have position of 1 and price moves 1 dollar (or other price unit) up"

    • fullName

      public final String fullName
      Full instrument name on the platforms where it's available, null otherwise

    • isFullDepth

      public final boolean isFullDepth
      True if data provided for instrument is full depth data

    • sizeMultiplier

      public final double sizeMultiplier
      Used when size granularity is less than 1 (for most providers it's always 1, so you can ignore this field if only those are targeted). This is only a visual thing, as all updates should still be performed in integer units. It was introduced mostly because of cryptocurrencies - since sizes are no longer integer values, you can premultiply all sizes by certain value and specify it in this field. E.g. 1000 will make bookmap display size of 1 as 0.001.

    • isCrypto

      public final boolean isCrypto
      Allows bookmap to distinguish crypto instruments from other types. If true - this instrument is a cryptocurrency or is based on cryptocurrencies in some way

    • recordingTag

      public final String recordingTag
      Used to distinguish local history with special modes on the per instrument basis (i.e. local history with delayed data vs live data) Provider should set this field to specify special mode of this instrument,"DELAYED" for example
      Note: it is recommended to not set this field for LIVE instruments for backward compatibility of historical servers, i.e. so the historical server returned "live" data to the user with the old client

    • isApiProtected

      public final boolean isApiProtected
      If this flag is set to true, then all add-ons, except those marked with UnrestrictedData annotation, will be blocked from receiving data from this instrument

  • Constructor Details

  • Method Details