API documentación

3

Reject (3)

A Reject (35=3) will be sent when a session-level error was detected in the FIX message sent by the client. This usually happens due to malformed data.

Campos

  • Etiqueta
    Nombre

    Header

    RequisitoY
    Descripción

    Standard header, with 35=3.

  • Etiqueta45
    Nombre

    RefSeqNum

    RequisitoY
    Descripción

    The MsgSeqNum (34) of the referenced message.

  • Etiqueta371
    Nombre

    RefTagID

    RequisitoN
    Descripción

    The tag number of the referenced FIX field.

  • Etiqueta372
    Nombre

    RefMsgType

    RequisitoN
    Descripción

    The MsgType (35) of the referenced message.

  • Etiqueta373
    Nombre

    SessionRejectReason

    RequisitoY
    Descripción

    The number that represents the reason for the reject. Supported values: 0 = Invalid tag number 1 = Required tag missing 2 = Tag not defined for this message type 3 = Undefined tag 4 = Tag specified without a value 5 = Value is incorrect (out of range) for this tag 6 = Incorrect data format for value 9 = CompID problem 10 = SendingTime accuracy problem 11 = Invalid MsgType (35) 13 = Tag appears more than once 14 = Tag specified out of required order 15 = Repeating group fields out of order 16 = Incorrect NumInGroup count for repeating group 17 = Non "Data" value includes field delimiter (character) 99 = Other

  • Etiqueta58
    Nombre

    Text

    RequisitoN
    Descripción

    Message

  • Etiqueta
    Nombre

    Trailer

    RequisitoY
YObligatorio: incluya este campo en todos los mensajes.
NOpcional: puede omitirse.
N*Obligatorio condicionalmente — opcional a menos que se indique lo contrario en la descripción (busque (*)).
Alipay
Stripe
Eurex
AWS
Azure
Google Cloud
Currenex
Velocity Trade
Bitcoin
CME
Interactive Brokers
Kraken
FIX API
XTX
Bloomberg
Binance

Lanza tu plataforma.

Empieza.