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

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

• /Prematch_Tips – tips for future games (fixtures) (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

Host: engage.lsports.eu Port: 5671 (AMQP 0-9-1 over TLS)

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

• /fixtures → _{CustomerPackageId}_

• /Inplay_Tips → _{CustomerPackageId}_

• /Prematch_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.

Inplay_Tips

Subscribe to /Inplay_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.

Prematch_Tips

Subscribe to /Prematch_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.