My Funded Perpetuals changed this help center article on November 22, 2026. UpdatedStricter
Article now requires API key authentication, compression negotiation, and enforces connection limits; adds error handling and code examples.
What this means
Market data streaming changed from public access (no API key required) to requiring a live API key in the Authorization header of the WebSocket upgrade request. Permessage-deflate compression changed from recommended to required. Connection limit per API key added at 5 active connections. Error handling, HTTP status codes, WebSocket close codes, and troubleshooting guidance added. TypeScript and Python code examples added with proper authentication and event handling. Transition period provided via developer notice email with X-Developer-Feed-Auth and X-Developer-Feed-Enforce-At headers for checking readiness.
Subscribe to live prices, order books, trades, and candles over the public WebSocket API.
Connect
− Open wss://api-stream.myfundedperpetuals.com/v1/market-data. Market data is
− public: no API key, cookie, or authentication frame is required. Use this dedicated endpoint for developer integrations. Never send your trading API key to this
− socket. Live and sandbox trading use the same market feed.
− Send one JSON object per WebSocket text frame. Enable permessage-deflate
− compression in your WebSocket client: books, trades, and candles are several
− times smaller compressed. Keep one long-lived connection and multiplex your
− subscriptions on it; do not reconnect to poll for a fresh snapshot. This stream carries market
− observations; submit orders through the REST API.
− Market prices do not guarantee the price or size of a simulated fill.
Subscribe to live prices, order books, trades, and candles over the public WebSocket API.
Connect
− Open wss://api-stream.myfundedperpetuals.com/v1/market-data. Market data is
− public: no API key, cookie, or authentication frame is required. Use this dedicated endpoint for developer integrations. Never send your trading API key to this
− socket. Live and sandbox trading use the same market feed.
− Send one JSON object per WebSocket text frame. Enable permessage-deflate
− compression in your WebSocket client: books, trades, and candles are several
− times smaller compressed. Keep one long-lived connection and multiplex your
− subscriptions on it; do not reconnect to poll for a fresh snapshot. This stream carries market
− observations; submit orders through the REST API.
− Market prices do not guarantee the price or size of a simulated fill.
− javascript theme={null}
+ Open wss://api-stream.myfundedperpetuals.com/v1/market-data. Use this
+ dedicated endpoint for developer integrations. Live and sandbox trading use the
+ same market feed. This stream carries market observations; submit orders
+ through the REST API. Market prices do not guarantee the
+ price or size of a simulated fill.
+ Every connection must:
+ 1. Send an API key. Put a live API key in the Authorization header of the
+ WebSocket upgrade request as Bearer fp_live_.... Any read-only or
+ read-and-trade key from API Key Settings
+ works. Create a dedicated read-only key for market data: it cannot place
+ orders if it leaks. Sandbox keys (fp_test_), affiliate keys, and CLI or
+ MCP sessions are refused. Browsers cannot set this header on a WebSocket,
+ so connect from a server or script.
+ 2. Negotiate compression. Enable the permessage-deflate extension. Books,
+ trades, and candles are several times smaller compressed. Python
+ websockets and the Node ws package negotiate it by default; if your
+ client has a compression option, leave it on.
+ 3. Stay within 5 connections per API key. One connection carries every
+ market you need, so multiplex subscriptions on it. Another key of yours
+ has its own 5.
+ [!NOTE]
+ These requirements take effect on the date given in our developer notice
+ email. Until then, connections without a key or compression still work. Check
+ the X-Developer-Feed-Auth header on the upgrade response to see whether your
+ client is ready: authenticated means it meets every requirement, and any
+ other value is the error code your connection will receive once they apply
+ (unverified means the key had not been checked yet; reconnect after a few
+ seconds to see its result). X-Developer-Feed-Enforce-At shows the effective
+ time once it is scheduled.
+ Keep one long-lived connection and multiplex your subscriptions on it; do not
+ reconnect to poll for a fresh snapshot. Send one JSON object per WebSocket
+ text frame.
+ [tab] TypeScript (Node)
+ ts theme={null}
+ import WebSocket from "ws"; // negotiates permessage-deflate by default