Skip to main content
WebSocket failures arrive as frames, not HTTP status codes. There are two kinds. An error on one subscription does not close the connection or affect other subscriptions.

​
Protocol Errors

Failures not tied to a single subscription arrive on the error channel:

​
Subscription Errors

Failures tied to one subscription arrive on subscriptionResponse, with error attached to the echoed subscription:

​
Rejected Types

/ws accepts Spot channels including userTwapHistory. Perpetual-specific types such as clearinghouseState and userFundings are rejected as not applicable for spot; use /ws/perp (Testnet-Only) for those channels. Other unregistered channels are rejected, not silently subscribed.

​
Silent Failure

One case produces no error at all. A well-formed but non-existent coin, for example FOO/BAR, passes validation because the WebSocket layer has no market registry. The subscription succeeds and never receives data, and snapshot types return an empty payload. Validate symbols against Markets & Currencies before subscribing.

​
REST Errors

REST responses use a different shape. See Errors.