Connection & Consumption Setup

Connecting to LSports - RabbitMQ

So you've started to implement LSports services via RMQ, great choice! Let's get your connection running with a few simple steps.

This guide is intended to provide a better understanding of how the LSports Support team works to resolve issues in a timely manner and with minimal effort on your part.

The following example refers to these credentials: Username: MyEmail Password: Passw0rd1234 Package: 102030 (You should use the credentials provided by LSports)

Note: All examples below are written in C#.

When implementing your code, you need to get the RMQ library here. Please be aware that LSports currently uses version 3.12.10

1. Start off by making sure that your distributor connection is enabled by sending an API call as follows: https://stm-api.lsports.eu/Distribution/Start - Enable https://stm-api.lsports.eu/Distribution/Stop - Disable Method - POST

Body Scheme

{
    "PackageId": PackageId,
    "UserName": "UserName",
    "Password": "Password"
}

Response:

JSON

{
  "type": "object",
  "properties": {
    "Header": {
      "type": "object",
      "properties": {
        "HttpStatusCode": {
          "type": "integer"
        }
      },
      "required": [
        "HttpStatusCode"
      ]
    },
    "Body": {
      "type": "object",
      "properties": {
        "Message": {
          "type": "string"
        }
      },
      "required": [
        "Message"
      ]
    }
  },
  "required": [
    "Header",
    "Body"
  ]
}

If the package was enabled the message should contain "Value was already set". For any other status or error message, please recheck your credentials or contact us.

1. Create a connection factory as follows:

ConnectionFactory connectionFactory = new ConnectionFactory
{
    HostName = "Described below",
    Port = 5672,
    UserName = "MyEmail",
    Password = "Passw0rd1234",
    AutomaticRecoveryEnabled = true,
    VirtualHost = "StmPreMatch", //For PreMatch
    VirtualHost = "StmInPlay", //For InPlay
    RequestedHeartbeat = 580,
    NetworkRecoveryInterval = TimeSpan.FromSeconds(1)
};

RMQ HostName: InPlay: stm-inplay.lsports.eu PreMatch: stm-prematch.lsports.eu

1. Create a connection as follows:

IConnection connection = _connectionFactory.CreateConnection();

1. Create a model as follows:

IModel model = connection.CreateModel();

1. Configure the quality of service:

model.BasicQos(prefetchSize: 0, prefetchCount: 100, global: false);

1. Consume message:

EventingBasicConsumer consumer = new EventingBasicConsumer(model);
consumer.Received += (sender, eventArgs) =>
{
    // Deserialize message
    // Call method to handle deserialized message
};

Tip: You can access SportId directly from the RabbitMQ message headers — no need to deserialize the payload first. This is useful if you want to route or filter messages by sport before processing them.

if (eventArgs.BasicProperties.Headers != null 
    && eventArgs.BasicProperties.Headers.TryGetValue("SportId", out var sportIdObj))
{
    string sportId = Encoding.UTF8.GetString((byte[])sportIdObj);
    // Route message based on sport
}

SportId is available on all message types except Keep Alive (31) and Heartbeat (32). See RabbitMQ Header for the full list of available headers.

1. Start message consumption: (make sure to type in your package ID using underscores ('_') as describes) For example, if package ID was “102030”

model.BasicConsume(queue: "_102030_", noAck: true, consumer: consumer)

• From here you should be able to pull up your RMQ connection and start receiving Heartbeat messages.
• The maximum consumers allowed is 60; once the limit is exceeded, the package will be automatically disabled.

Note: Before connecting more than 1 consumer, implement a message sorting mechanism to avoid data discrepancies.

Staying up to date and recovering

When you subscribe to a fixture on TRADE, the first message you receive is a complete picture, including all data for the fixture and its markets. This is followed by updates (deltas) that only reflect changes to the data.

If you ever disconnect from the TRADE feed, follow the recovery sequence in Reliability & Recovery: it covers reconnection order, snapshot usage, and how to reconcile snapshot data with cached RMQ messages.

Possible error types

Note: If the queue reaches 10000 unread/unpacked messages it will be automatically purged and your distributor connection will be disabled.

Most failed connection attempts occur due to incorrect credentials or incorrect connection details. Here are the most common errors and possible solutions:

"Connection failed" - Please check that the connection details i.e. Connection factory, RMQ host, VirtualHost were typed correctly. "Access refused"- Please check that your package is enabled and the login credentials and package ID were typed correctly.

For an in-depth explanation of our data structure, you may continue reading our documentation. Now all you need to do is, to start ordering our sports data according to your specific needs. An email notification will be sent to your contacts upon deletion of your queue