Technical Integration

Step 1: Access Credentials

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

You will receive access to two RabbitMQ virtual hosts:

• /fixtures – pre-event metadata

• /tips – real-time tips (added/removed)

---

Step 2: Queue Provisioning

For each vhost, LSports provisions a queue per customer.

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

Encoding: UTF-8 JSON

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

---

Step 3: Establish Connections

Connect to the RabbitMQ broker using your credentials:

Host: tips-inplay.lsports.eu (for Tips InPlay) or tips-prematch.lsports.eu (for Tips PreMatch)

Port: 5671 (TLS/SSL)

Virtual Host: /fixtures or /tips (depending on data type)

Authentication: Use the username and password provided by your CSM

Open two AMQP connections (one per vhost) and consume from the same queue name on each vhost:

• /fixtures → _{CustomerPackageId}_

• /tips → _{CustomerPackageId}_

Integration examples in C#, Python, and Java appear under Code Samples below.

Step 4: Data Mapping

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

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

• Use add or update: unknown fixture ⇒ add; known fixture ⇒ update changed fields.

Tips: subscribe to /tips and correlate by body.fixtureId against your fixtures store.

• Two message kinds: Added (1) and Removed (2).

• For Added, you get full tip objects; for Removed, you get IDs to remove.