-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aggregates will return information from multiple cusips #5
Comments
Can you please hide your API key in the request URL? We have plans to implement a solution to ensure only the ticker you are looking for is returned, however, I do not have a concrete ETA to give you at this time. So sorry this has troubled you! |
Thanks for the heads up - I didn't realize it was in the dataset title additionally. No worries - please just keep me in the loop :-). |
If polygon-io/issues#201 is fixed this issue becomes far lower priority as I can trim the search criteria by the initial listing date. |
Adding the enhancement tag, as this is related to querying data tracked across the most recent active ticker, instead of returning data for all tickers associated with a ticker. |
Any update of polygon-io/issues#201 ? |
URL
https://api.polygon.io/v2/aggs/ticker/ULTR/range/1/day/2012-03-17/2022-03-17?adjusted=true&limit=50000&apiKey={...}
Result
Expected Result
The ULTR ETF started around august 2019. The system is picking up some information from the ULTR etf and some information from another cusip on a different exchange that used the same ticker. What I personally would like is to only get information on the ETF. Due to issue polygon-io/issues#201 I can't use the list_date to shorten the request date ranges.
This means that in general I can't trust the aggregate call in order to build out backtesting information because it will potentially switch cusips in the same data stream.
The text was updated successfully, but these errors were encountered: