WebSockets provide a persistent connection between your application and Pragma’s servers, allowing for real-time data streaming with minimal latency.

​
Connection Endpoints

wss://ws.devnet.pragma.build/node/v1
We recommend using the Development endpoint while building and testing your application.

​
Authentication

All WebSocket connections are currently public and open without authentication.
In the near future, WebSocket connections will require authentication using an API key similar to the REST API. We recommend designing your implementation with this upcoming change in mind.

​
Connection Management

Connection Lifecycle

Understanding how to properly establish, maintain, and close WebSocket connections is essential for reliable real-time data streaming.

Reconnection Strategy

Implement proper reconnection logic to handle network interruptions and server-initiated disconnects gracefully.

​
Connection Limits

​
Best Practices

1

Implement proper error handling

Always include robust error handling and reconnection logic in your WebSocket implementation. Network disconnections and server-side issues can occur, and your application should gracefully recover from these scenarios.
2

Use ping/pong messages

Send regular ping messages (every 30 seconds) to keep the connection alive and detect stale connections early.
3

Monitor connection health

Track connection state and performance metrics in your application to ensure reliable data delivery and prompt detection of issues.
4

Implement backoff strategy

When reconnecting after failures, use an exponential backoff strategy to avoid overwhelming the server during outages.

​
Common Issues & Troubleshooting