axsx Posted Friday at 08:34 PM Report Posted Friday at 08:34 PM (edited) SPY chart and connect symbol is blank, price multiplier is 1 and offset is 0. convert = yes in dashboard (maybe it has to be NO) Edited Friday at 08:36 PM by axsx
axsx Posted Friday at 08:40 PM Report Posted Friday at 08:40 PM NQ chart and connect symbol is blank. Rest defaults (price multiplier is 10 defaults). Truth engine uses QQQ to get option chain and convert, but spot price is wrong in dashboard. I dont see the put and call and flip etc.
axsx Posted Friday at 08:45 PM Report Posted Friday at 08:45 PM nq chart with connect symbok $NDX ; price multiplier is 1 offset is 0.
axsx Posted Friday at 08:50 PM Report Posted Friday at 08:50 PM I think one important decision to make is For nq and es futures we have to do autoconvert, the symbols to be used are SPY and QQQ. For any other instrument, we have to use it directly in schawab to see if we get the option chain, if not we have to map to a closet ETF option chain stored in a internal table/array. this is with no autoconvert flag in the NT indicator parameters. Giving price multiplier and offset without autoconvert flag will be misleading. all thee or none imo.
Ninja_On_The_Roof Posted Saturday at 06:06 AM Report Posted Saturday at 06:06 AM It is so great having an indicator named after you huh Kimsam?🥰 kimsam 1
kimsam Posted Saturday at 10:09 AM Author Report Posted Saturday at 10:09 AM 4 hours ago, Ninja_On_The_Roof said: It is so great having an indicator named after you huh Kimsam?🥰 Haha limited edition 😄Every detail counts .. Name is just part of the user experience 😌 Harrys and jquiroz75 2
axsx Posted Sunday at 12:47 AM Report Posted Sunday at 12:47 AM (edited) @kimsam SPX charts with old and new versions. Old version works perfectly, schwab fetches SPX option chain ( I think it is not fetching spy, you can verify in code). The new version, auto convert is false, price multiplier is 1, connect symbol is SPX. The fetch of SPX fails. Can you check why ? my guess is due to return code of 400, the API call in the latest version of code might have an issue. I checked with NQ similarly, I see the same issue. NDX also same issue. Edited Sunday at 01:03 AM by axsx
axsx Posted 17 hours ago Report Posted 17 hours ago @kimsam Can you please post the latest kimsamgex when you get time. Thanks
garban Posted 11 hours ago Report Posted 11 hours ago On 3/27/2026 at 10:20 PM, babaluFlow said: My API registration wasn't approved. Is there another way?Kimsam Got denied in api registration also.Wonder how they choose to approve
Predict Posted 3 hours ago Report Posted 3 hours ago (edited) My account is approved. Can anyone help me? I've entered my API key and secret key. I'm using the new Kim Sam Gex.cs indicator, but no data is coming in. How can I check this? Edited 3 hours ago by Predict
kimsam Posted 3 hours ago Author Report Posted 3 hours ago (edited) Recommend use the old one .. for now U need to add in the indicator setting the symbol.. es or other .. Edited 3 hours ago by kimsam
Predict Posted 2 hours ago Report Posted 2 hours ago You mean the old one SchwabConnector.cs ? That one give me compile error NetMQ
Predict Posted 1 hour ago Report Posted 1 hour ago I think we should add new file which with clear description. To many files we have. 1. Do we need to change always TCP Port if yes why if not what is the standard port 2. Connect Sym: leave blank or not 3. Do we have to use the indicator on Future Contract ? I really don’t know why it won’t work.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now