massive-com / massive-com/client-js

Free plan cannot run websocket example (ws-library-advanced.js)

Open
#290 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
273
Forks
74
Avg merge
7h 58m
Merged PRs (30d)
11

Description

Hi team,

I created a free Massive account to test the websocket example in examples/websocket/ws-library-advanced.js.

After inserting my API key and running the example, I receive this message:

Status Update: Connected Successfully
Status Update: Your plan doesn't include websocket access. Visit https://massive.com/pricing to upgrade.

This means I cannot connect to the websocket at all. Since the official example for the JS client includes websocket usage, I’m trying to understand:

  • Is there any way to test websocket functionality on the free plan?
  • If not, is there an alternative example or sandbox environment where developers can evaluate websocket features before upgrading?
  • Or should the documentation clarify that websocket examples require a paid plan?

Steps to reproduce:

  1. Create a free Massive account
  2. Generate an API key
  3. Run ws-library-advanced.js with that key
  4. Observe the “plan doesn’t include websocket access” message

Expected behavior:
Ability to test websocket functionality or guidance on how to evaluate it without upgrading.

Actual behavior:
Connection is rejected due to plan limitations.

Thanks in advance for any clarification.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with examples/websocket/ws-library-advanced.js and reproduce the free-plan response using the steps in the issue. Check the example and nearby documentation for plan requirements, then clarify the supported evaluation path or state that websocket access requires an eligible plan. Done means free users can understand the limitation and what they can test.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
api, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.