Skip to main content
CoinGecko WebSockets are available through Uniblock with separate validation and WSS endpoints.

​
Endpoints

  • WebSocket (WSS): wss://lively-dust-7404.lively-fog-f2d9.workers.dev/coingecko
  • HTTP (Validation): https://lively-dust-7404.lively-fog-f2d9.workers.dev/coingecko/validate

​
Authentication

  • Include the X-API-KEY header in both validation and connection requests.

​
Workflow

  1. Validate the request with the HTTP endpoint.
  2. Connect to the WSS endpoint.
  3. Send your CoinGecko message payload after the connection is established.

​
Connection heartbeat

CoinGecko requires a heartbeat to keep the stream open and detect idle connections:
  • Server ping: CoinGecko sends a ping frame every 10 seconds.
  • Client pong: Your client must respond with a pong frame within 20 seconds.
  • Termination: If no pong is received within that 20-second window, the connection is closed automatically.
  • Library behavior: Most WebSocket libraries handle ping/pong control frames automatically, but you should verify your client is not blocking or suppressing them.
CoinGecko uses different message types than standard JSON-RPC-style WebSocket flows. Refer to the official CoinGecko WebSocket documentation for the expected message formats.

​
Example validation request

curl --request GET \
  --url 'https://lively-dust-7404.lively-fog-f2d9.workers.dev/coingecko/validate' \
  --header 'X-API-KEY: YOUR_UNIBLOCK_API_KEY'

​
Pricing

Responses are billed using the shared WebSocket pricing formula:
  • 0.1 CU * 3181.819 per response returned