Schwab tells me that the symbols for the NDX and the XAU indexes are $NDX and $XAU. But when I enter these symbols into MW, there is no data. Does anyone else have this problem? It appears that somehow MW is getting confused over this. Schwab tells me:
Thank you for reaching out to the Schwab Trader API Support Team.
The Trader API will use the same symbols as Schwab.com (not thinkorswim), so for indices, you will typically need to include a $ at the beginning of the symbol.
For example: $NDX, $XAU, etc.
When I do this, MW returns different symbols than what I entered ($XAU.X or XAU or $NDX.X or NDX). Perhaps there is some leftover code related to TDAmeritrade, which needs to be changed due to the Schwab changeover.
UPDATE: what Schwab has told me:
The Trader API will use the symbol $NDX for the 'NASDAQ 100 INDEX' and the symbol $XAU for the 'PHLX GOLD SILVER INDEX CAPITAL-WEIGHT'. I just tested the GET /quotes endpoint for both of those tickers, and am not seeing any issues with returning the expected quote data on our side.
Have you contacted MotiveWave directly regarding those symbols? There may be an issue with the symbology mapping on their side that is potentially causing the issue.
Thank you for reaching out to the Schwab Trader API Support Team.
The Trader API will use the same symbols as Schwab.com (not thinkorswim), so for indices, you will typically need to include a $ at the beginning of the symbol.
For example: $NDX, $XAU, etc.
When I do this, MW returns different symbols than what I entered ($XAU.X or XAU or $NDX.X or NDX). Perhaps there is some leftover code related to TDAmeritrade, which needs to be changed due to the Schwab changeover.
UPDATE: what Schwab has told me:
The Trader API will use the symbol $NDX for the 'NASDAQ 100 INDEX' and the symbol $XAU for the 'PHLX GOLD SILVER INDEX CAPITAL-WEIGHT'. I just tested the GET /quotes endpoint for both of those tickers, and am not seeing any issues with returning the expected quote data on our side.
Have you contacted MotiveWave directly regarding those symbols? There may be an issue with the symbology mapping on their side that is potentially causing the issue.
Attachments
Last edited: