Skip to content

Releases: polygon-io/client-jvm

v5.1.2

03 Jan 20:02
3ad9ed1
Compare
Choose a tag to compare

What's Changed

Full Changelog: v5.1.1...v5.1.2

v5.1.1

15 Dec 19:10
0a15ad7
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v5.1.0...v5.1.1

v5.1.0

03 Nov 21:54
14395f6
Compare
Choose a tag to compare

Release Notes: Support for "Universal" Snapshots Endpoint

This brings client-jvm support for the recently added v3/snapshot endpoint, which accepts a list of up to 250 tickers of any asset class and returns a paginated list of all their snapshots.

An example of how to use this feature within client-jvm is available here!

What's Changed

Full Changelog: v5.0.0...v5.1.0

v5.0.0

02 Nov 14:39
895faee
Compare
Choose a tag to compare

Release Notes: WebSocket Syntax and Parsing Enhancements

This release has a breaking change to the WebSocket API's PolygonWebSocketClient connection syntax that significantly improves and paves the way for supporting a broader range of products in the future. Please update your WebSocket API implementations accordingly, and as always, we value your feedback and are here to support you through this transition.

We've provided fully fleshed-out example clients for all subscription types here: GitHub - polygon-io/client-jvm.

New Connection Requirements:

  • When initializing a connection using PolygonWebSocketClient, it is now mandatory to specify a Feed (e.g., Feed.RealTime) and a Market (e.g., Market.Stocks).
  • Subscription definitions have been updated as well. To subscribe to data, you must use the new PolygonWebSocketSubscription format, like so: PolygonWebSocketSubscription(PolygonWebSocketChannel.Stocks.AggPerMinute, "*").

Why This Change?
This update brings clarity to what you're subscribing to and we greatly improved the message parsing logic, ensuring a robust foundation for integrating upcoming products with ease.

What's Changed

Full Changelog: v4.6.0...v5.0.0

v4.6.0

25 Oct 20:58
e154916
Compare
Choose a tag to compare

Breaking Changes in WebSocket Connection Syntax

We recently rolled out significant updates to our WebSocket API, including changes to connection syntax and message parsing via #122. These changes were intended to be released as a major version update, reflecting the breaking changes introduced. However, they were inadvertently released as a minor version that would normally go into a major release (e.g. we should have bumped the version from v4.5.0 to v5.0.0). We apologize for any confusion or inconvenience this may have caused.

Please see the release notes for v5.0.0 for a summary of the changes and updated syntax.

What's Changed

Full Changelog: v4.5.0...v4.6.0

v4.5.0

25 Jul 22:12
0fac1d6
Compare
Choose a tag to compare

Added Support For Second Aggs

What's Changed

New Contributors

Full Changelog: v4.4.0...v4.5.0

v4.4.0

12 Jun 19:31
eea9099
Compare
Choose a tag to compare

Added Support for Launchpad WS

What's Changed

New Contributors

Full Changelog: v4.3.0...v4.4.0

Add Support for New Indices Endpoints

22 Mar 19:13
20ca09a
Compare
Choose a tag to compare

What's Changed

Full Changelog: v4.2.1...v4.3.0

Fix type for shareClassSharesOutstanding in ticker details response

01 Feb 14:56
eb29b7f
Compare
Choose a tag to compare

Minor Breaking Change

While this is not a major version release, a bug-fix in this release introduced a very minor breaking change:
shareClassSharesOutstanding inside the TickerDetails response class changed type from Int? to Long? to support large amounts of shares outstanding (shoutout to @wangtieqiao for finding and contributing this fix!).

What's Changed

New Contributors

Full Changelog: v4.2.0...v4.2.1

Support options chain snapshot

04 Jan 23:43
9c9b760
Compare
Choose a tag to compare

Support for the new options chain snapshot API, and fix issues with jitpack.io distribution of the package

What's Changed

Full Changelog: v4.1.0...v4.2.0