Skip to main content
Remember to create your project and get your API key through the Uniblock dashboard.
Uniblock WebSockets let you connect to supported provider streams through a single Uniblock-managed access layer. This gives you a consistent authentication model, unified billing, and provider-specific WebSocket access without managing separate credentials for each provider. This section includes support for Alchemy, Ankr, CoinGecko, Codex, GoldRush, and Helius.

​
How it works

WebSocket integrations use a two-step handshake:
  1. Call the provider’s HTTP validation endpoint first.
  2. Open a connection to the matching WSS endpoint using the same request details.
  3. Send the provider-specific subscription or message payload after the socket connects.
This validation step helps confirm that your API key and required parameters are present before a long-lived WebSocket connection is established.
Try validation first in Postman before opening a persistent WebSocket connection in your application.

​
Authentication

Most Uniblock WebSocket endpoints use the X-API-KEY header. Some providers, such as Codex, pass the Uniblock API key as a required query parameter. For full authentication details, see Authentication.

​
Supported providers

​
Chain coverage

WebSockets are scoped to what each underlying provider streams, not to the full list of chains covered by Uniblock’s HTTP APIs. Availability for a specific chain depends on the provider you connect through. For the exact chain identifiers accepted by Uniblock’s HTTP APIs, see the Chains overview. A chain listed there is not guaranteed to have a WebSocket path unless it is covered by one of the providers above.

​
Pricing

WebSocket costs are calculated per response returned:
  • Formula: 0.1 CU * 3181.819 per response returned
Actual usage depends on the number of responses your subscriptions receive. For provider-specific pricing and connection limits, see Usage & Limits.