WebSocket Connection
This guide explains how to establish a secure WebSocket (WSS) connection to the RMS-Socket service for receiving real-time updates from the DEFEND Risk Management System.
Overview
The RMS-Socket service provides real-time event streaming via secure WebSocket connections. Clients receive instant updates for betting approval operations without polling the API. The betting approval operations accrued on the bet-slips that getting to "Bet Referral" page and they are manually approved or rejected.
Key Features:
Secure WebSocket (WSS) connections
Real-time message broadcasting
Customer-platform isolated rooms
Support for multiple event types
Supported Events:
RESERVE_BET_ACCEPT
Reserved bet acceptance notifications
RESERVE_BET_REJECT
Reserved bet rejection notification
Connection Requirements
Endpoint
Production
wss://rms.lsports.cloud
Path: /rms-socket/socket.io
Required Headers
Authorization
String
Yes
Bearer token
Bearer <accessToken>))gf)from ARENA360 authentication
Refer to the Authentication Guide for obtaining access tokens.
Authentication
Before establishing a WebSocket connection, you must obtain a valid access token using your ARENA360 API credentials.
Refer to the Authentication Guide for steps on:
Generating API tokens in ARENA360
Exchanging credentials for access tokens
Refreshing expired tokens
Important Notes:
Access tokens expire every 30 minutes
Refresh tokens are valid for 7 days
Include the access token in the
Authorizationheader as:Bearer <accessToken>
Rate Limiting
To protect the service, the following rate limits are enforced:
WebSocket Connections
10 connections
Per minute per IP
HTTP Requests
100 requests
Per 15 minutes per IP
Exceeding these limits will result in a 429 Too Many Requests error.
Next Steps
Quick Start & Best Practices - Get connected in minutes
Code Examples - Complete examples in JavaScript, Python, and Browser
Error Handling - Error codes and troubleshooting guide
Last updated
Was this helpful?