Example Security Definition Request
8=FIX.4.2|9=90|35=c|49=jphsecdef|56=test|34=2|52=20180823-19:07:25|320=test| 321=3|207=ICE|167=FUT|55=BRN|10=076|
Helpful notes on Sec Def Requests
- Tag 320 needs to be unique per request
- Tag 321 if provided has to be set to 3 (list securities)
- At minimum Exchange(207) or MIC (100) & Security(167) have to be included
- For more detail symbol (55) can also be added
Example Security Definition
8=FIX.4.2|9=00408|35=d|49=test|56=jphsecdef|34=2|52=20180823-19:07:13.418|320=test|322=test:0|323=4|393=78|15=USD|167=FUT|55=BRN|107=Brent Crude Futures|200=201808|541=20180831|205=31|48=12661575418721668990|207=ICE|100=IFEU|18211=M|16460=1000|16463=1|16464=N|16552=0.01|16554=1000|18223=201810|454=5|455=BRN FMV0018!|456=98|455=BRN Oct18|456=97|455=GB00H1JWRP15|456=4|455=LCO8|456=5|455=222462|456=8|864=1|865=5|866=20180831|10=101|
Helpful notes tracking Security Definitions
- Tag 320 should be the same as the request
- Tag 322 is the unique ID for that security definition
- Tag 323 response - with successful request should always be 4
- Tag 393 total num securities - this will show the number of definitions coming back in the response. The total received should equal the number in 393. (note:Sec Def Requests are by default subscriptions. New contracts will dynamically be added, as long as the FIX client is connected. Which will in turn alter the value in tag 393)
Contributors
13 People are following this .
