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