Skip to main content
Connect a Solana WebSocket client to the complete wss:// URL copied from the dashboard. The location token is the first path segment, exactly as in the HTTPS URL.

​
Methods

Every method whose name ends in Subscribe or Unsubscribe is forwarded. Each has its own page with parameters, notification format, and a real exchange captured from ThorEdge. blockSubscribe and voteSubscribe are not enabled on the upstream node and return -32601 Method not found.

​
Example

Send after the socket opens:
The first frame back is the subscription id, then one notification per slot:

​
Authentication

Unlike HTTPS, a WebSocket connection is authenticated by the token only; the token must be present.

​
Subscription cap

Active subscriptions are counted per location token across all of its connections, so the cap follows you through reconnects until the old subscriptions are unsubscribed or their connections close. Read the value under Limits in the dashboard. A subscribe request over the cap is not forwarded. The client receives:
Unsubscribing, or closing the connection, releases the slots.

​
Connection behavior

  • ThorEdge does not send keepalive pings and has no idle timeout of its own; ping and pong frames pass through in both directions.
  • Request and notification frames are relayed unchanged. WebSocket traffic does not count against the RPS cap.
  • After a reconnect, resubscribe and reconcile any state you missed through HTTPS.

​
Next steps