Technical Integration

Welcome!

This guide will help you connect to LSports' Engage Hyper LiveScore Feed and its complementary Fixtures Feed.

Step 1: Access Credentials

Get your Username, Password, and CustomerPackageId from your CSM.

Step 2: Establish Connections

RabbitMQ Host: hyper-livescore.lsports.eu

Open two AMQP connections (one per vhost):

• Fixtures

• Incidents

Queue name (both vhosts): _{CustomerPackageId}_

Encoding: UTF-8 JSON

Transport: AMQP 0-9-1 over TLS (port 5671)

Step 3: Data Mapping

Fixtures: subscribe to Fixtures and persist by body.fixtureId.

Delta updates only (messages are sent only on change).

Incidents: subscribe to Incidents and correlate by body.fixtureId against your fixtures store.

Step 4: Go Live

Coordinate with your CSM for production readiness and final checks.

First-Time Integration Guide

When integrating for the first time, you will not automatically receive fixture messages for matches that already exist in our system - messages are only sent when fixture state changes.

Recommended Integration Steps

Step 1: Establish Connections Set up your RabbitMQ consumers for both queues (see Technical Integration section)

Step 2 : Maintain Continuous Consumption

• Keep both queue consumers running continuously

• Fixtures Queue: Update your local store on each delta message

• Incidents Queue: Correlate incoming incidents with stored fixtures by fixtureId

Step 3: Initial Snapshot Use the Snapshot API to populate your fixtures database:

• Call the Trigger Snapshot endpoint (see API Documentation section)

• This publishes all upcoming fixtures (not yet started) to your Fixtures Queue

• Consume and store these fixtures locally

Step 4: Handle Disconnections

• Implement automatic reconnection logic

• Monitor queue depth to avoid approaching the message purge limit

• Consider implementing backpressure mechanisms for bulk message processing