when receiving feeds for XBO symbols, is there a way to tell the original Exchange that sends the bid/ask, or the bid/ask is also XBO composite so Exchange info is not available? We saw quote updates, for example, LRDGBP.xbo, either one entry of:
or entry of the following:
we can't tell if it's from LSE, BATS, CHIX, or Turquoise. Thanks.
Our xbo service was designed for MIFID I (we are slowly moving into the updated legislation of MIFID II at the start of 2018) and so has been around for a while now.
It contains quote and post-trade data from the primary venue (LSE, Euronext etc depending on the instrument and country you select) plus also a couple of the main MTFs from that market. The list used to be bigger but now it is typically Tuquoise, BATs and Chi-X Europe (BATs and Chi-X are differing platforms but both owned by CBOE). Its not the same as the US consolidated quote where you get the NBBO from all venues in the tape eg IBM shows the NBBO for all venues that trade IBM.
The xbo RICs will only show the best BID and ASK from the venues that are listed under the "0# RIC" eg 0#VODGBP.xbo which for London is VODl.BS, VODl.CHI and VODl.TQ as well as VOD.L.
You can see the source RIC the BID and ASK comes from by looking at ASK_RIC and BID_RIC respectively. The venue the latest trade price has come from is in TRD_P_XID and BUYER_ID and SELLER_ID performs the same function for the BID and ASK respectively.
Any further questions please let me know.
It could be BUYER_ID and SELLER_ID fields. Followings are the definitions of these fields.
BUYER_ID: Venue code from FID 1709 on source RIC, for update that is being applied to the FID 22 (BID). If there is more than one venue with the same bid, the first (earliest) venue should be held followed by an asterisk. SELLER_ID: Venue code from FID 1709 on source RIC for update that is being applied to the FID 25 (ASK). If there is more than one venue with the same ask, the first (earliest) venue should be held followed by an asterisk.
However, to confirm it, please submit a question to the content support team via Contact Us page.