📄️ Using the API
To interact with our WebSocket API, establishing a connection to the WebSocket server is the first step. This connection is initiated by connecting to our WebSocket endpoint using the WSS protocol, which ensures that the data exchanged between the client and server is encrypted and secure.
📄️ Authenticating
When using the Emogg WebSocket API, it's crucial to authenticate your connection immediately after it's established. The first message you send should always be an authentication message. Failure to authenticate promptly will result in the server terminating the connection.
📄️ Rate limits
To ensure a fair and efficient use of the Emogg WebSocket API for all users, we've implemented several rate limits. These limits are designed to prevent excessive usage that could affect the stability and reliability of the service. It's important to be aware of these limits to manage your application's behavior and avoid interruptions.
🗃️ Auth
1 items
🗃️ Channels
5 items
📄️ Ping
Ping the connection to check connectivity. This endpoint can also be used to reset the idle connection timeout and avoid connection being dropped by the server.