Hi, I’m working on a personal finance dashboard and would like to know the exchange the symbol was traded on so that i can retrieve the correct OHLC data from a third party API. So far the closest thing I can find to this information is the ticker field on the order endpoint which seams to be inconsistent and am not confident that it can be relied on in a programmatic way. E.g. US tickers follow this format “AREC_US_EQ” and British tickers look like “BPl_EQ” (notice the lowercase l after the symbol). This inconsistency is confusing and doesn’t give me confidence about the ticker. Could you please include the exchange as an additional field in the response. e.g. like LSE/NYSE/NASDAQ or the MIC like XLON/XNYS.
Thank you.
Hi,
I work in the industry, and there is no equivalent to say a ‘SWIFT’ standard to this.
Much like how ISINs can be multi listed and represent a stock in different currencies on different exchanges.
We need an ‘open banking’ industry change to this. Issue is much bigger imo.
Welcome to the T212 API.
I have accessed all of the API endpoints and built my own SQLServer tables and I refresh them frequently.
I cannot argue with any of the points you make in your postings. I have tried to match tickers with symbols from other providers without success.
It’s just one of the irritations associated with the T212 API. Another is that T212 will change the endpoints without notice though, mercifully, they have not done so since November last year when wholesale changes were made.
After that change I reported a definite bug in the Order History endpoint. It was fixed but I was never fully sure that it was bug free. I just gave up on it. The undocumented reverse chronological sequence of Order History retrieval is also annoying.
For me though, the lower case first character of the exchange names was never a problem as SQLServer by default does caseless comparisons.
Hi, I embarked on a similar project. What I ended up doing is to cache the information from the instruments and exchanges endpoints to start with. Then grab the T212 Ticker, which is unique on T212. Find your ticker in the instruments data and grab the shortName and the WorkingScheduleId. Exchanges can have multiple working schedules but each ID will match to only one exchange. Once I had the correct exchange names I built a table of exchange names and the suffixes I need to built a Yahoo-conform ticker symbol.
So for AstraZeneca the shortName is AZN and the suffix for LSE is .L - makes AZN.L, which Yahoo recognizes.
I have difficulties to describe my feelings about this procedure without turning the air blue, but until T212 decides to put a bit of thought into the API, I guess it will have to do.