jrbell19
commented
2 years ago We may be able to do this in the future, however, we would likely just add pagination logic to the responses that would query the next individual ticker.
Open papadeus opened 2 years ago
jrbell19
commented
2 years ago We may be able to do this in the future, however, we would likely just add pagination logic to the responses that would query the next individual ticker.
matichenor
commented
2 years ago Consolidating https://github.com/polygon-io/issues/issues/130 into this ticket.
Is your feature request related to a problem? Please describe. Getting all stocks to consume a lot of time and I'm sure a lot of resources
Describe the solution you'd like Ticker details API should allow multiple tickers in one API
Describe alternatives you've considered Ticker details API should allow multiple tickers in one API
Additional context example /v1/meta/symbols/AAPL,MSFT/company
RaccoonWang
commented
1 year ago +1, would like to see this implemented ASAP
Diogomartf
commented
6 months ago Yes, I need this, is it implemented already? Are plans to add this in the future?
It is frustrating when we need to make the same call repeatedly for different tickers. For example, if we want aggregates for the same period and options but for 1,000 tickers, it requires 1,000 API calls. It would be much nicer if an array of tickers could be passed in and an array of results returned. This applies to ALL stock endpoints.
Varying tickers are the biggest frustration but there are times when other fields could also be arrays, for example the timestamp of Quotes NBBO VX (I want last quote for a given ticker at an array of timestamps)
Example: POST: /v2/aggs/tickers BODY: { "tickers": ["MSFT","AAPL","TSLA"], "multiplier": 2, "from": "2021-01-02", "to": "2021-01-03" }
OR (this would have query length limitations but would still be an improvement) GET: /v2/aggs/tickers/range/{multiplier}/{timespan}/{from}/{to}?tickers=AAPL,TSLA,MSFT,...