Powered By SignalR


SignalR Service

HexaEight SignalR Service powers Flow, Patcher and Communicator Platoforms allowing any Web, Mobile, Desktop and IOT Clients to communicate in real-time using Instant Message Delivery System. You can scale to any number of connections and have messages delivered to all your clients instantly. All your client need is your API Key. Any client connected using any of your API key will receive the Message. All clients connected will remain connected Forever unless forcibly disconnected.


Messaging Platform Features

Real Time Communication

Realtime Messaging is the Backbone of every automation platform. Our SignalR Service Platform provides this capabilitiy and allows our Robots to remain connected 24x7 and exchange data messages with each other in Real-Time.  Our Real time platform can also be used by your own Clients to add real time communication capabilities.


Additional Clients can be added on the fly and there is no limitation to the number of simultaneous connections that can be extended to your application or product.


All communication within our platforms are protected by end to end encryption. This means your data remains safe during transit at all times.


We built our platforms keep developers in mind.  Hence we provided a feature for locking messages that will be very useful especially when contention for a resource occurs in a messaging platform.

Delivery Verification

The messaging platform ensures a copy of the message is also received  by the sender to ensure that the sender knows that the communication of the sent message was a success


HexaEight Messaging Platform uses the least used Transport Protocol called Long Polling and converts it to the best offered Service by ensuring there is no disconnection.

Support for multiple Clients

Any SignalR Client using different languages can establish connection to our Platform. Sample Code is instantly available for reference for JavaScript and .NET Core Clients.

Cost Effective

The Messaging platform has a simple pricing so that it benfits everyone from using our Platform without thinking about balooning costs in the long run.

Code Samples

Code Sample for for different SignalR Clients is available below.

Quick VB.Net Code Sample

Ensure to establish connections like below

connection = New HubConnectionBuilder().WithUrl("https://hexaeight-signalr-service.p.rapidapi.com/services/signalr", Microsoft.AspNetCore.Http.Connections.HttpTransportType.LongPolling, Function([option])
[option].AccessTokenProvider = Function() Task.FromResult(("sometoken" + ":" + "secretkey"))
[option].Headers.Add("x-rapidapi-host", "hexaeight-signalr-service.p.rapidapi.com")
[option].Headers.Add("x-rapidapi-key", "yourkey")
End Function).WithAutomaticReconnect.Build()

Ensure to add your RAPID API Keys and RAPID API HOST In the Headers as shown in the code samples before making a request.
Ensure to define a client method called "BroadcastMessage" to receive messages.
The Server Method "SendMessage" can be invoked to send a message
The Server Method "Lock" can be invoked to lock a message
The Server Method "Release" can be invoked to release a message 

Locks is a new feature that allows you to lock a message. This feature is useful in situations where multiple connections are contending for a resource. For example assume there are multiple bidders in a chat channel and the first bidder for a price gets to hold that bid, In this scenario, you can send a lock message with a unique token and secret key with message BID=1000 and in a multi connection scenario, the message will get locked to the first bidder and you will get a response that the message is locked. The same unique token + secret combination can release the locked message.

Lock Messages are CASE SENSITIVE. Lock Messages will automatically be released if not reacquired within 2 minutes. If you wish to continue to keep holding a lock keep re-acquiring the lock within 2 minutes by sending a lock message from the same connection that initiated the lock. Lock Messages cannot be sent if you dont set the Authorization header. 

Authorization Header Format : token followed with colon followed with secret key like token:secretkey

Sample Messages:
Keep Alive Token : {"token":"Keep Alive","time":"132187761456753627","message":"637098993456753651"}
Message : {"token":"sometoken","time":"1574301051","message":"Hello"}
Locked Message : {"token":"sometoken Locked","time":"1574301066","message":"BID=1000"}
Released Message : {"token":"sometoken Released","time":"1574301066","message":"BID=1000"}

All Clients once connected remain connected unless disconnected. Keep alive Messages are sent to all clients every 45 seconds to determine their connection status and remain connected. If you have not received a keep alive message for more than 90 seconds, consider your connection disconnected and you will have to re-establish connection.

If you need a HTTPs Endpoint to post your messages or data like a IOT HUB and receive the messages in SignalR Client, simply post the message to /notifyclients followed by a token identifier and all your SignalR Clients will get a copy of the message that can be further processed. This is useful in situations when you want to use our Services as a IOT Hub for message processing.

HexaEight SignalR Service Provider

HexaEight SignalR Messaging Service is available via RAPIDAPI and can be subscribed from our Service Provider's Page. 


(c) Copyright 2019 HexaEight All Rights Reserved

Terms of Use                                            Privacy Policy

This site uses cookies to give you the best experience.