RULE CHANGE
Market data streaming
Maximum providers per subscription increased from 6 to 10; account streaming capability added for order and fill updates; 3 other changes to documentation.
What this means
The maximum number of providers per subscription changed from 6 to 10. The firm introduced account streaming for real-time order, fill, position, and balance changes on trader accounts, while REST remains available for snapshots and lookups. The documentation clarified that omitting providers on market channels matches every public provider rather than using a compatibility set. A source URL was added to the article.
▸ View exact changes
The change in place, line by line
Before Nov 11, 2026
Market data streaming
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}
Market identity and filters
Use the exact coin and provider returned for your selected market by
GET /v1/markets or GET /v1/markets/{market_id} in the REST API.
Pass coin in the subscription's symbols array. REST's symbol is a display
label: for Binance BTC, symbol is BTC and coin is BTCUSDT, so subscribe
to symbols: ["BTCUSDT"] with providers: ["binance"]. Provider values
are hyperliquid, binance, bybit, veranta, ostium, lighter, fpx,
and synthetic. FX uses veranta (for example EURUSD and USDJPY). The
retiring Hyperliquid EUR/USD and USD/JPY markets (xyz:EUR and xyz:JPY)
keep publishing while positions remain on them. The historical fpx and
lighter identities are retired and no longer publish market data.
Every market subscription requires symbols with 1 to 32 exact symbols.
− providers is optional, but specify it to avoid mixing venue prices.
− Omitting it uses the compatibility provider set, so explicitly name new
− providers. status accepts only providers and needs no symbols.
| Channel | Payload fields | Event type |
|---|---|---|
| ticks | symbols, optional providers | tick |
| books | symbols, optional providers | book |
| trades | symbols, optional providers | trade |
| candles | symbols, optional providers, intervals, historyLimit | candle |
| marketStats | symbols, optional providers | marketStats |
| status | Optional providers | providerStatus |
For candles, request explicit intervals such as intervals: ["1m"].
Accepted interval names are 1s, 1m, 3m, 5m, 15m, 30m, 1h,
2h, 4h, 8h, 12h, 1d, 3d, 1w, and 1M. Availability depends
on the provider. historyLimit: 0 skips retained candle replay; a positive
value limits it. Omitting it replays the retained backlog. Use
clear connection-local IDs and mappings, reconnect with exponential backoff
and jitter, and re-establish subscriptions. Restore books and prices from the
new snapshot, backfill missing candles with candles.history, and reconcile
account trading state through the trading API. A market trade tape cannot be
used as your account fill ledger. A slow client can lose superseded state or
be disconnected; always monitor freshness.
On draining, connect a replacement, subscribe, wait for its initial snapshot
boundaries, and then close the old socket. Deduplicate overlapping events.
If the replacement fails, keep reading the old socket until it ends and retry
with backoff. Avoid unlimited reconnect loops on permanent filter errors.
| Bound | Behavior when exceeded |
|---|---|
| 256 active subscriptions per connection | New subscription rejected. |
−
| Bound | Behavior when exceeded |
|---|---|
| 32 symbols and 6 providers per subscription | Invalid filter rejected. |
| 64 distinct provider/symbol leases across candle, book, and trade subscriptions per connection | New subscription rejected. |
| 16 concurrent requests, including at most 4 history requests per connection | Excess request returns an error; heartbeat pings are excluded. |
| 512 active connections per source address | Upgrade rejected with HTTP 429. |
| 30 connection admissions per minute per source, with a burst of 10 | Excess upgrades return HTTP 429 with Retry-After: 60. |
| Shared process connection, memory, and upstream budgets | Upgrade may return HTTP 503 or subscription/request may be rejected. Retry transient capacity failures with backoff. |
These budgets belong to the developer stream and are separate from the website feed.
The service also limits simultaneous history work and one-shot status requests;
prefer a status subscription and back off when capacity is exhausted. Keep one multiplexed socket per
client, unsubscribe unused views, cache closed candles, and avoid polling REST
quotes for every price update. Market streaming adds no REST quota usage.
− Account balances, positions, orders, and fills are available through REST.
− Private account streaming is not available.
− This documentation is built and hosted on Mintlify, a developer documentation platform.
After Nov 12, 2026
Market data streaming
+ Source: https://docs.myfundedperpetuals.com/market-streaming
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}
Market identity and filters
Use the exact coin and provider returned for your selected market by
GET /v1/markets or GET /v1/markets/{market_id} in the REST API.
Pass coin in the subscription's symbols array. REST's symbol is a display
label: for Binance BTC, symbol is BTC and coin is BTCUSDT, so subscribe
to symbols: ["BTCUSDT"] with providers: ["binance"]. Provider values
are hyperliquid, binance, bybit, veranta, ostium, lighter, fpx,
and synthetic. FX uses veranta (for example EURUSD and USDJPY). The
retiring Hyperliquid EUR/USD and USD/JPY markets (xyz:EUR and xyz:JPY)
keep publishing while positions remain on them. The historical fpx and
lighter identities are retired and no longer publish market data.
Every market subscription requires symbols with 1 to 32 exact symbols.
+ providers is optional. On market channels, omitting it matches every public
+ provider, so specify it to avoid mixing venue prices. status accepts only providers and needs no symbols.
| Channel | Payload fields | Event type |
|---|---|---|
| ticks | symbols, optional providers | tick |
| books | symbols, optional providers | book |
| trades | symbols, optional providers | trade |
| candles | symbols, optional providers, intervals, historyLimit | candle |
| marketStats | symbols, optional providers | marketStats |
| status | Optional providers | providerStatus |
For candles, request explicit intervals such as intervals: ["1m"].
Accepted interval names are 1s, 1m, 3m, 5m, 15m, 30m, 1h,
2h, 4h, 8h, 12h, 1d, 3d, 1w, and 1M. Availability depends
on the provider. historyLimit: 0 skips retained candle replay; a positive
value limits it. Omitting it replays the retained backlog. Use
clear connection-local IDs and mappings, reconnect with exponential backoff
and jitter, and re-establish subscriptions. Restore books and prices from the
new snapshot, backfill missing candles with candles.history, and reconcile
account trading state through the trading API. A market trade tape cannot be
used as your account fill ledger. A slow client can lose superseded state or
be disconnected; always monitor freshness.
On draining, connect a replacement, subscribe, wait for its initial snapshot
boundaries, and then close the old socket. Deduplicate overlapping events.
If the replacement fails, keep reading the old socket until it ends and retry
with backoff. Avoid unlimited reconnect loops on permanent filter errors.
| Bound | Behavior when exceeded |
|---|---|
| 256 active subscriptions per connection | New subscription rejected. |
+
| Bound | Behavior when exceeded |
|---|---|
| 32 symbols and 10 providers per subscription | Invalid filter rejected. |
| 64 distinct provider/symbol leases across candle, book, and trade subscriptions per connection | New subscription rejected. |
| 16 concurrent requests, including at most 4 history requests per connection | Excess request returns an error; heartbeat pings are excluded. |
| 512 active connections per source address | Upgrade rejected with HTTP 429. |
| 30 connection admissions per minute per source, with a burst of 10 | Excess upgrades return HTTP 429 with Retry-After: 60. |
| Shared process connection, memory, and upstream budgets | Upgrade may return HTTP 503 or subscription/request may be rejected. Retry transient capacity failures with backoff. |
These budgets belong to the developer stream and are separate from the website feed.
The service also limits simultaneous history work and one-shot status requests;
prefer a status subscription and back off when capacity is exhausted. Keep one multiplexed socket per
client, unsubscribe unused views, cache closed candles, and avoid polling REST
quotes for every price update. Market streaming adds no REST quota usage.
+ For order, fill, position, and balance changes on your own accounts, use
+ account streaming. REST remains available for snapshots
+ and lookups.
Market data streaming
+ Source: https://docs.myfundedperpetuals.com/market-streaming
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}
Market identity and filters
Use the exact coin and provider returned for your selected market by
GET /v1/markets or GET /v1/markets/{market_id} in the REST API.
Pass coin in the subscription's symbols array. REST's symbol is a display
label: for Binance BTC, symbol is BTC and coin is BTCUSDT, so subscribe
to symbols: ["BTCUSDT"] with providers: ["binance"]. Provider values
are hyperliquid, binance, bybit, veranta, ostium, lighter, fpx,
and synthetic. FX uses veranta (for example EURUSD and USDJPY). The
retiring Hyperliquid EUR/USD and USD/JPY markets (xyz:EUR and xyz:JPY)
keep publishing while positions remain on them. The historical fpx and
lighter identities are retired and no longer publish market data.
Every market subscription requires symbols with 1 to 32 exact symbols.
− providers is optional, but specify it to avoid mixing venue prices.
− Omitting it uses the compatibility provider set, so explicitly name new
− providers. status accepts only providers and needs no symbols.
+ providers is optional. On market channels, omitting it matches every public
+ provider, so specify it to avoid mixing venue prices. status accepts only providers and needs no symbols.
| Channel | Payload fields | Event type |
|---|---|---|
| ticks | symbols, optional providers | tick |
| books | symbols, optional providers | book |
| trades | symbols, optional providers | trade |
| candles | symbols, optional providers, intervals, historyLimit | candle |
| marketStats | symbols, optional providers | marketStats |
| status | Optional providers | providerStatus |
For candles, request explicit intervals such as intervals: ["1m"].
Accepted interval names are 1s, 1m, 3m, 5m, 15m, 30m, 1h,
2h, 4h, 8h, 12h, 1d, 3d, 1w, and 1M. Availability depends
on the provider. historyLimit: 0 skips retained candle replay; a positive
value limits it. Omitting it replays the retained backlog. Use
clear connection-local IDs and mappings, reconnect with exponential backoff
and jitter, and re-establish subscriptions. Restore books and prices from the
new snapshot, backfill missing candles with candles.history, and reconcile
account trading state through the trading API. A market trade tape cannot be
used as your account fill ledger. A slow client can lose superseded state or
be disconnected; always monitor freshness.
On draining, connect a replacement, subscribe, wait for its initial snapshot
boundaries, and then close the old socket. Deduplicate overlapping events.
If the replacement fails, keep reading the old socket until it ends and retry
with backoff. Avoid unlimited reconnect loops on permanent filter errors.
| Bound | Behavior when exceeded |
|---|---|
| 256 active subscriptions per connection | New subscription rejected. |
−
| Bound | Behavior when exceeded |
|---|---|
| 32 symbols and 6 providers per subscription | Invalid filter rejected. |
+
| Bound | Behavior when exceeded |
|---|---|
| 32 symbols and 10 providers per subscription | Invalid filter rejected. |
| 64 distinct provider/symbol leases across candle, book, and trade subscriptions per connection | New subscription rejected. |
| 16 concurrent requests, including at most 4 history requests per connection | Excess request returns an error; heartbeat pings are excluded. |
| 512 active connections per source address | Upgrade rejected with HTTP 429. |
| 30 connection admissions per minute per source, with a burst of 10 | Excess upgrades return HTTP 429 with Retry-After: 60. |
| Shared process connection, memory, and upstream budgets | Upgrade may return HTTP 503 or subscription/request may be rejected. Retry transient capacity failures with backoff. |
These budgets belong to the developer stream and are separate from the website feed.
The service also limits simultaneous history work and one-shot status requests;
prefer a status subscription and back off when capacity is exhausted. Keep one multiplexed socket per
client, unsubscribe unused views, cache closed candles, and avoid polling REST
quotes for every price update. Market streaming adds no REST quota usage.
− Account balances, positions, orders, and fills are available through REST.
− Private account streaming is not available.
− This documentation is built and hosted on Mintlify, a developer documentation platform.
+ For order, fill, position, and balance changes on your own accounts, use
+ account streaming. REST remains available for snapshots
+ and lookups.