Massive API (formerly Polygon.io)
GET /benzinga/v1/news version retirement
Stopped workingSubscribe to Massive API (formerly Polygon.io)Share
Calls to GET /benzinga/v1/news on Massive API (formerly Polygon.io) stopped working on December 1, 2025.
Calls it hits
GET /benzinga/v1/news
What to use instead of these calls
Migrate your calls to GET /benzinga/v2/news instead. Moving to the replacement requires adapting your integration to its small breaking changes.
In Massive API (formerly Polygon.io)'s words
The Benzinga News v1 API has been officially sunset and is no longer available. Users should migrate to the Benzinga News v2 API
Facts
- API
- Massive API (formerly Polygon.io)
api.massive.com - Kind
- Version retirement
- Takes effect
- December 1, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Massive API (formerly Polygon.io)'s own pages
Questions
When does this change take effect?
Calls to GET /benzinga/v1/news on Massive API (formerly Polygon.io) stopped working on December 1, 2025.
What happens to calls after December 1, 2025?
They have failed since December 1, 2025.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Massive API (formerly Polygon.io) 1
-
GET /vX/reference/financialsEndpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.