2. Configuring Providers & API Keys

Provider configuration lives under the Data provider tab of Chart Settings: the active provider, the connection mode, the Massive API key, and the streaming feed. Binance needs no configuration.

Frontend vs. backend mode

The connection mode decides where provider requests run:

Use Backend mode when you want to keep your Massive key on the server instead of shipping it to the browser.

Environment variables

When running the app from source, configure keys in a .env.local file:

# Backend / server-side Massive key (used in Backend mode)
MASSIVE_API_KEY=your_massive_api_key_here
MASSIVE_STOCKS_WS_FEED=delayed

# Frontend / browser-exposed Massive key (used in Frontend mode)
NEXT_PUBLIC_MASSIVE_API_KEY=your_massive_api_key_here
NEXT_PUBLIC_MASSIVE_STOCKS_WS_FEED=delayed

• MASSIVE_API_KEY is used by backend chart routes.
• NEXT_PUBLIC_MASSIVE_API_KEY is bundled for the browser and is required when Massive is the active frontend provider.
• The *_WS_FEED variables set the default websocket feed (realtime or delayed).

The NEXT_PUBLIC_ key is exposed to the browser by design. In public deployments, prefer Backend mode so the secret key stays on the server.

Entering a Massive key in the app

You can also set the browser Massive key directly in Settings → Data provider. It is stored in your browser's local storage on this device (not synced across devices). The streaming feed can be overridden per browser under Settings → Data provider → Massive → Streaming.

Binance

Binance crypto data uses public Spot REST and websocket endpoints, so it needs no API key and no configuration — opening a pair like BTCUSDT just works.

Next steps

Learn how symbols are typed and resolved.

Next: Symbols & Ticker Formats