开云体育

Bart, There is no problem buying any multileg combo since there is always an ask even for OTM strikes. Getting out of a spread/combo when there is no bid on any one leg is impossible even with a

Ace, I see - these are liquidity and margin-requirement issues with trading individual legs of a spread. Which is why I had in my example vertical spreads for both orders, so you have “defined

All of this is because 0DTE SPY/QQQ options combos exit orders oftentimes don't get executed because a long leg has totally decayed and has no bid. That's why I want to manage each leg instead of the

Jurgen, Do you think it checks for any execution or a full order filled? Because if as soon as one contract of the main order is filled the companion market order gets triggered with more contracts,

This seems to confirm what I thought: They don’t do string validation on the entered ‘symbol’ when entering it via the API so it just accepts anything and since it’s called ‘underlying’ in

Thank you for letting us know. The local symbol does not seem to work and it probably needs to be what the contract calls "symbol" (though please try yourself and confirm). I tried it Sunday evening

Thanks Jürgen! I made a quick test today an an execution condition on SPY to sell QQQ and it worked. I will try with options tomorrow using the options contract localSymbol as the symbol: IB doesn't

Hi both, This "SPY 231108C00430000" is not the conid because I've always seen a long numeric when looking for the conid of an instrument. You can check also the conid of an options contract by

Thanks. It will try this in the coming week when the exchange is open. I’m still sceptical for 2 reasons: 1. The TWS dialog specifies to enter the “underlying” and so that would be “SPX” not

Just realized you were looking for an SPX option. As expected, TWS accepts an execution condition for "SPXW 231115C04350000" via the API as well:

I don't have too much hands-on experience with options, Bart. But TWS did accept an order I just placed via TWS API in a paper account with this ExecutionCondition: * symbol="SPY 231108C00430000" *

The "Contract ID" (aka conId) uniquely identifies all attributes of an instrument except, potentially, the exchange. When you retrieve contracts for an instrument (

Jurgen, thank you for the suggestion - obviously that should be the 'accepted answer' IF it works. But I'm not sure it does for a specific option contract as the OP asked for. When I try this in TWS,

Hi Jurgen, I think it doesn't monitor any "conid" execution, instead just symbol, sectype and exchange, does this equals to the conid of an instrument? (<TwsApiOnGroupsIo@...>)

We don't know all requirements, but a simple Execution Condition ( https://interactivebrokers.github.io/tws-api/order_conditions.html#execution_condition ) on Order 2 should do the trick. Not sure why

Order.hedgeType as pair probably? Never tried this though.

No

In the last two months, I've noticed my code that loops over symbols and requests historical bar data with ib_insync has significantly slowed down.? I'm aware of the pacing guidelines and stay within

hi there, I have a Paper account. I have set up a subscription for reqHistoricalData as below. the contract I am using is AAPL, exchange="SMART". https://www.youtube.com/watch?v=qqlgiGQA5Vs I get the

Log in to the Client Portal and go to "Settings". Under "User Settings" go to "Research Subscriptions". Select "Manage Subscriptions". Turn on "Wall Street Horizon Corporate Event Data for Retail