Skip to content

Releases: massive-com/client-js

v10.7.0

27 Apr 14:25
ac59b97

Choose a tag to compare

What's Changed

Full Changelog: v10.6.0...v10.7.0

v10.6.0

07 Apr 11:04
d8a2112

Choose a tag to compare

What's Changed

Full Changelog: v10.5.0...v10.6.0

v10.5.0

03 Mar 14:10
530792a

Choose a tag to compare

What's Changed

Full Changelog: v10.4.0...v10.5.0

v10.4.0

24 Feb 23:57
db2b2e2

Choose a tag to compare

What's Changed

Full Changelog: v10.3.0...v10.4.0

v10.3.0

05 Feb 18:01
1fb446e

Choose a tag to compare

What's Changed

Full Changelog: v10.2.0...v10.3.0

v10.2.0

26 Jan 05:59
af5eb46

Choose a tag to compare

Significant Update to Futures Beta Endpoints

As part of our ongoing beta program for Futures data, we've made a key structural improvement by consolidating endpoints. Previously, we had separate endpoints for retrieving lists of all Futures items (e.g., contracts, products, or schedules) and for fetching details on specific ones. Now, we have single streamlined endpoints:

  • /futures/vX/contracts: Handles both lists and specific contract details.
  • /futures/vX/products: Covers product lists and individual product info.
  • /futures/vX/schedules: Manages overall and product-specific schedules.
  • /futures/vX/market-status: Enhanced for better market insights.

This consolidation simplifies integration and reduces API calls, but it introduces breaking changes.

New Endpoints for Expanded Coverage

We've added several new endpoints to enrich your toolkit:

  • /benzinga/v1/bulls-bears-say: Sentiment analysis from bulls and bears.
  • /fed/v1/labor-market: Insights into Federal Reserve labor market data.
  • /stocks/vX/float: Stock float metrics.
  • /stocks/filings/10-K/vX/sections: Breakdown of 10-K filing sections.

What's Changed

Full Changelog: v10.1.0...v10.2.0

v10.1.0

11 Dec 21:39
1e53d1e

Choose a tag to compare

What's Changed

Full Changelog: v10.0.0...v10.1.0

v10.0.0

08 Dec 17:17
f69b126

Choose a tag to compare

Release Notes - Massive JS Client v10.0.0 (breaking changes)

This major release introduces a breaking change to improve the developer experience by fixing a bug in API function signatures. Previously, when we switch to auto generating the client based on the openapi specification, the endpoints were generated with positional parameters, which cluttered function calls, especially for those with many optional params. This required passing explicit undefined values as placeholders which is pretty painful for endpoints with many optional params. This mismatched user expectations and documented examples. Now, all request parameters are bundled into a single required object (requestParameters), making signatures cleaner, more readable, and flexible. Developers can omit optional properties altogether, aligning with modern TypeScript practices and reducing friction.

Before:

import { restClient } from '@massive.com/client-js';

const apiKey = "XXXXX";
const rest = restClient(apiKey, 'https://api.massive.com');

async function example_listTickers() {
  try {
    const response = await rest.listTickers(
      undefined,
      undefined,
      market,
      undefined,
      undefined,
      undefined,
      undefined,
      search,
      undefined,
      undefined,
      undefined,
      undefined,
      undefined,
      undefined,
      limit
    );
    console.log('Response:', response);
  } catch (e) {
    console.error('An error happened:', e);
  }
}

example_listTickers();

After:

import { restClient } from '@massive.com/client-js';

const apiKey = "XXXXX";
const rest = restClient(apiKey, 'https://api.massive.com');

async function example_listTickers() {
  try {
    const response = await rest.listTickers({
      market: "stocks",
      active: "true",
      order: "asc",
      limit: "100",
      sort: "ticker"
    });
    console.log('Response:', response);
  } catch (e) {
    console.error('An error happened:', e);
  }
}

example_listTickers();

What's Changed

Full Changelog: v9.1...v10.0.0

v9.1

24 Nov 19:17
afeba05

Choose a tag to compare

Release Notes – Massive JS Client v9.1 (breaking changes)

This is a major breaking release of the JS 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.

Breaking Changes

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

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

Migration Guide

To upgrade:

npm install --save '@massive.com/client-js'

Then update your imports:

import { restClient } from '@polygon.io/client-js'; # Old
import { restClient } from '@massive.com/client-js'; # 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

What's Changed

Full Changelog: v8.2.0...v9.1

v8.2.0

14 Aug 19:36
25d8ff7

Choose a tag to compare

What's Changed

Full Changelog: v8.1.0...v8.2.0