search

polygon-io / issues

Quickly track and report problems with polygon.io
29 stars 0 forks source link

Discrepancies for tickers with special characters between reference and data endpoints #270

Open fplein opened 1 year ago

fplein commented 1 year ago

This issue relates to stocks that at some point in time had a ticker containing a special character. I will illustrate it based on BATR.A vs BATRA.

URL https://api.polygon.io/v3/reference/tickers?date=2016-06-28&search=BATR&active=true

https://api.polygon.io/v3/reference/tickers/BATRA?date=2016-06-28 https://api.polygon.io/v3/reference/tickers/BATR.A?date=2016-06-28

https://api.polygon.io/v3/trades/BATRA?timestamp=2016-06-28 https://api.polygon.io/v3/trades/BATR.A?timestamp=2016-06-28

Result In the reference endpoints, the ticker is shown as BATR.A (return NOTFOUND for BATRA). The data relating to this stock however is available under BATRA (no data returned for BATR.A)

Expected Result The reference API should return the ticker under which data is stored (i.e. BATRA instead of BATR.A).

Desktop (please complete the following information):

Additional context Note that many of the stocks that are concerned by this issue at some point switch the ticker when running historically over the reference endpoints, i.e. BATR.A at some point in time, but BATRA at a different point in time, where BATRA is found most frequently. See e.g. https://api.polygon.io/v3/reference/tickers?date=2016-10-28&search=BATR&active=true.

AHangstefer commented 12 months ago

Hi! Thanks for bringing this to our attention. I've let our engineering team know.

mlathan commented 10 months ago

Hi! I also reported an issue regarding special characters in a ticker (in my case it was '/') in #231. The Tickers Endpoint does return tickers with '/'. But when you request Ticker Details for them on that specific date in the past you also get a HTTP/1.1 404 Not Found. Same issue ... '.' or '/' in the ticker.

The issue was closed with a proposed data inacurate workaround which is ... query another ticker (use '.' instead of '/'). Not the ticker I wanted. From an API point of view it is an error. When a ticker X containing a '/' is historically reported for a date D there must be a successful answer for Ticker Details of X on that date D,