API documentation

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.

Fields

  • Tag
    Name

    Header

    ReqY
    Description

    Standard header, with 35=3.

  • Tag45
    Name

    RefSeqNum

    ReqY
    Description

    The MsgSeqNum (34) of the referenced message.

  • Tag371
    Name

    RefTagID

    ReqN
    Description

    The tag number of the referenced FIX field.

  • Tag372
    Name

    RefMsgType

    ReqN
    Description

    The MsgType (35) of the referenced message.

  • Tag373
    Name

    SessionRejectReason

    ReqY
    Description

    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

  • Tag58
    Name

    Text

    ReqN
    Description

    Message

  • Tag
    Name

    Trailer

    ReqY
    Description
YRequired — include this field in every message.
NOptional — may be omitted.
N*Conditionally required — optional unless noted in Description (look for (*)).
Alipay
Stripe
Eurex
AWS
Azure
Google Cloud
Currenex
Velocity Trade
Bitcoin
CME
Interactive Brokers
Kraken
FIX API
XTX
Bloomberg
Binance

Запустите свою платформу.

Начать работу.