Skip to content
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

Scheduled Delistings #6

Open
jamesfulford opened this issue Jan 16, 2022 · 1 comment
Open

Scheduled Delistings #6

jamesfulford opened this issue Jan 16, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@jamesfulford
Copy link

Is your feature request related to a problem? Please describe.

As an algorithmic trader, I want to avoid holding securities that will be delisted the next trading day, so I can invest elsewhere.

Describe the solution you'd like

The /v3/reference/tickers endpoint only provides "delisted_utc" when "active=false" - only reports after-the-fact that a ticker has delisted. However, often (not always), we know that some tickers are scheduled to be delisted.

If we know a ticker is scheduled to be delisted, I want to know.

For example, ROVRW (a warrant) had news that the warrants would be exercised on 2022-01-12. I would like my code to ignore that opportunity.

Describe alternatives you've considered

I can check every warrant before I trade it - a human-in-the-loop model - though I'd rather not be chained to a desk with the strategies I'm developing.

Additional context

ENVXW was also delisted in January 2022, though without news.

I would also like it available historically (/v3/reference/tickers with day= query parameter), so I can backtest and see if delisting is scheduled for the following day. (if unexpected delisting, please don't edit historical view)

Some expectations:

  • best-effort (sometimes you don't see it coming, also might not be reported consistently)
  • can be mutable (maybe delisting is rescheduled)
@jamesfulford jamesfulford added the enhancement New feature or request label Jan 16, 2022
@jrbell19
Copy link
Collaborator

This is certainly something that we plan to offer in the future, however I do not have any kind of timeframe to expect.

We will be sure to follow up with updates as progress is made on this effort.

@jrbell19 jrbell19 transferred this issue from polygon-io/issues Mar 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants