v2.0.1

Release Notes – Massive Python Client v2.0.1 (breaking changes)

This is a major breaking release of the Python client as part of our company rebrand from Polygon.io to Massive.com. Polygon.io has rebranded as Massive.com effective October 30, 2025. Existing API keys, accounts, and integrations continue to work exactly as before. The only change in this SDK is that it now defaults to the new API base at api.massive.com, while api.polygon.io remains supported for an extended period. You can still install the old client using pip install polygon-api-client too.

Breaking Changes

• The default REST API base URL has changed from api.polygon.io → api.massive.com.
• The default WebSocket base URL has changed from socket.polygon.io → socket.massive.com.
• The package name and import path have changed from polygon → massive.

No other breaking changes are introduced. Core functionality, endpoints, and method signatures remain identical.

Migration Guide

To upgrade:

pip install massive

Then update your imports:

from polygon import RESTClient # Old
from massive import RESTClient # New

All API keys, accounts, and integrations continue to function without modification. If you continue using the legacy polygon-api-client package, it will remain supported for an extended transition period.

ℹ️ Additional Information

• No changes to client methods, models, or response structures.
• Both API domains (polygon.io and massive.com) are fully operational in parallel.
• For full background, see our blog post: Polygon.io is Now Massive.
• For help, open an issue or contact support@massive.com.

What's Changed

• Rebrand massive by @justinpolygon in #953

Full Changelog: v1.16.3...v2.0.1

v1.16.3

What's Changed

• Log request URL with the Response headers by @romanzdk in #952
• Update README.md by @justinpolygon in #948
• Bump orjson from 3.11.3 to 3.11.4 by @dependabot[bot] in #949
• Bump sphinx-autodoc-typehints from 2.0.1 to 2.3.0 by @dependabot[bot] in #950

Full Changelog: v1.16.2...v1.16.3

v1.16.2

What's Changed

• Use logging instead of print for traces by @romanzdk in #947
• Bump types-setuptools from 75.8.0.20250110 to 80.9.0.20250822 by @dependabot[bot] in #942
• Bump sphinx from 7.1.2 to 7.4.7 by @dependabot[bot] in #943
• Bump orjson from 3.10.15 to 3.11.3 by @dependabot[bot] in #944
• Bump pook from 2.0.1 to 2.1.4 by @dependabot[bot] in #945

New Contributors

• @romanzdk made their first contribution in #947

Full Changelog: v1.16.1...v1.16.2

v1.16.1

What's Changed

• Adds support for ETF Global endpoints by @justinpolygon in #940
• Add support for Futures snapshot endpoint by @justinpolygon in #939

Full Changelog: v1.16.0...v1.16.1

v1.16.0

Important Changes

Python Version Support: We've removed support for Python 3.8, and the new minimum version is 3.9. This should not introduce any breaking changes to your code or API usage, but it was necessary to update to the latest websockets library, which requires Python 3.9 or higher.

What's Changed

• Fix Python 3.14 compatibility for modelclass decorator (KeyError: 'annotations') by @justinpolygon in #932
• Upgrade to websockets 14+ and propagate ConnectionClosedError after max_reconnects by @justinpolygon in #935
• Adds support for stocks financials v1 endpoints by @justinpolygon in #933
• Adds support for Benzinga v2 news endpoint by @justinpolygon in #934
• Add individual futures exchange endpoints (CME, CBOT, NYMEX, COMEX) by @justinpolygon in #931
• Fix typo in documentation URL for options snapshots by @westonplatter in #929
• Update test.yml to remove python 3.8 by @justinpolygon in #936
• Bump certifi from 2025.6.15 to 2025.10.5 by @dependabot[bot] in #930
• Bump urllib3 from 2.2.3 to 2.5.0 by @dependabot[bot] in #937
• Remove unnecessary sqlite3 Timestamp import from summaries.py and indicators.py to fix mypy errors by @justinpolygon in #938
• Bump mypy from 1.13.0 to 1.14.1 by @dependabot[bot] in #823

New Contributors

• @westonplatter made their first contribution in #929

Full Changelog: v1.15.4...v1.16.0

v1.15.4

What's Changed

• fix: make resolution optional in list_futures_aggregates to include in query params by @justinpolygon in #926

Full Changelog: v1.15.3...v1.15.4

v1.15.3

What's Changed

• Sync benzinga, economy, furures, and tmx by @justinpolygon in #898

Full Changelog: v1.15.2...v1.15.3

v1.15.2

What's Changed

• Sync with latest futures beta spec by @justinpolygon in #897

Full Changelog: v1.15.1...v1.15.2

v1.15.1

What's Changed

• Sync futures aggs with latest spec by @justinpolygon in #894

Full Changelog: v1.15.0...v1.15.1

v1.15.0

What's Changed

In this release, we’ve added beta support for Futures, introduced a refactor to WebSocket event parsing to correctly handle overlapping event types across asset classes, and added an option to disable automatic pagination for greater control over result limits. We also fixed a bug related to using custom base URLs with the REST client.

Futures Support (Beta)

• Added beta support for Futures REST and WebSocket endpoints.

WebSocket Event Parsing Refactor

• WebSocket event types ("T", "Q", "A", "AM") are now reused across asset classes.
• Introduced MARKET_EVENT_MAP to resolve event types based on market context (e.g. stocks vs. futures).
• This allows accurate message deserialization and avoids cross-market parsing errors.

Note for custom WebSocket users: If you're manually processing WebSocket messages, you may need to update your logic to consider the market parameter for Futures messages.

Pagination Control

• Added support for disabling automatic pagination via pagination=False when instantiating RESTClient.
• When disabled, limit is treated as a total cap rather than a page size.
• Helps users fetch a fixed number of results without iterating over all pages.

Bug Fixes

• Fixed an issue where custom base URLs were not properly respected in REST requests.

Commits

• Bump requests from 2.32.0 to 2.32.4 by @dependabot in #885
• Bump certifi from 2025.4.26 to 2025.6.15 by @dependabot in #889
• Add futures beta support by @justinpolygon in #884

Full Changelog: v1.14.6...v1.15.0