Support Board
Date/Time: Fri, 10 Jan 2025 22:11:36 +0000
Gld orders not working
View Count: 950
| [2016-10-07 20:05:20] |
| User666549 - Posts: 4 |
|
Hi, I am receving data for GLD but I am unable to place orders. After many e mails with Interactive Brokers API support they have confirmed that GLD-STK-SMART/ARCA are the correct parameters but they are not being mapped to the right fields within Sierra Charts. IB wanted to me to let you know that you can contact API support directly at any time with questions. I have the exchange separator / set in the IB API settings. I also have the currency set to USD in Sierra Charts. Please Help, Todd |
| [2016-10-10 10:13:24] |
| |
|
This really goes to show just how ridiculously stupid and poorly designed the TWS API is. This is really really stupid on their part. The fact that there is such absurd, massive and ridiculous and inconsistent complexity regarding symbols. Interactive Brokers should be completely and totally ashamed of themselves over this garbage. There should be one single uniform symbol that is used for market data and trading. And they cannot even accomplish that. Ridiculous. We are looking into this. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2016-10-10 17:20:34
|
| [2016-10-11 07:24:17] |
| |
|
Communication with Interactive Brokers about this: On 2016-10-11 8:41 AM, IB API Services wrote:
> > Sorry for any confusion. I believe I am familiar with the client in question and he had also previously contacted us about defining the GLD stock contract. The issue he described to us was that he was unable to load charts for GLD. We explained that it is necessary to specify the 'primary exchange' field in addition to specify the exchange as 'SMART' but otherwise there was nothing special about this contract. > > From his log file, he was defining symbols in the wrong fields, such as currency = 'ARCA', which was generating an error. It should just be: > > Symbol: GLD > Security Type: STK > Exchange: SMART/ARCA > > However please note that to place smart-routed orders if the primary exchange is necessary that it won't be possible to use the component exchange separator- It would have to be: > > Symbol: GLD > Security Type: STK > Exchange: SMART > Primary Exchange: ARCA > > as separate fields. Otherwise error 200: "Invalid destination exchange specified" will be encountered because the 'exchange' field is used as the destination and exchange. Response: We confirmed that Sierra Chart does in the case of Symbols which use the notation "exchange/primary exchange", separate these two components when submitting an order. So it is just like this:
Symbol: GLD Security Type: STK Exchange: SMART Primary Exchange: ARCA It has been this way for some time now. It has not changed and we checked it just now. The only other contract item which is set is the currency which in this case is set to USD. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: