# Hyper LiveScore

## Quick Start

1. Go to **ENGAGE → Hyper → LiveScore**
2. Find your fixture using filters or search
3. Click the fixture to open Message Stream
4. Filter by incident type or Message ID
5. Copy Message ID for support or investigation

***

## What is Hyper LiveScore?

Hyper LiveScore is a self-serve investigation tool in Arena360 that shows exactly what Hyper sent for any match in near real-time.

**What you can see:**

* What was sent (incident type & values)
* When it was sent (timestamps & ordering)
* How certain it was (confidence score)
* Message ID for reference and troubleshooting

It turns raw live incidents into a practical investigation experience that improves transparency, speeds up troubleshooting, and reduces escalation to engineering.

**Typical scenarios:**

* A customer claims a goal arrived late → verify exact send time
* Trading wants to confirm which signal suspended a market → check confidence scores
* Support needs proof of what was sent at a specific second → copy Message ID
* Integration team sees a mismatch vs their ingestion → compare incident values and timing
* Compliance requires audit trail for a disputed incident → export evidence

***

## How to Access

Navigate to **ENGAGE → Hyper → LiveScore** in Arena360.

**Requirements:**

* Arena360 access under relevant Account
* Active Hyper LiveScore entitlement

***

## Fixture Selection

The Fixture List is your starting point to find the match you want to investigate.

### Sport Types Panel

Filter fixtures by sport using the left panel. The number shows available fixtures per sport. Click any sport to filter; use the **>** arrow for location/competition drill-down.

### Filters & Search

| Filter                 | Purpose                   |
| ---------------------- | ------------------------- |
| Fixture ID / Team Name | Text search               |
| Start Date             | Date picker (Apply/Clear) |
| Fixture Status         | Multi-select dropdown     |

**Available Fixture Statuses:**

| Status         | Description             |
| -------------- | ----------------------- |
| NSY            | Not Started Yet         |
| In Progress    | Match currently live    |
| Finished       | Match concluded         |
| Cancelled      | Match cancelled         |
| Postponed      | Postponed to later date |
| Interrupted    | Match interrupted       |
| Abandoned      | Match abandoned         |
| Lost Coverage  | Data feed lost          |
| About to Start | Starting imminently     |

### Results Table

Each row represents a fixture. Click any row to open Message Stream.

| Column      | Description      |
| ----------- | ---------------- |
| Start Date  | Scheduled start  |
| Location    | Country/region   |
| League      | Competition name |
| Fixture ID  | Unique ID        |
| Home / Away | Team names       |
| Status      | Current status   |

Table supports sortable columns, pagination (30/50/100 per page), and clickable rows.

***

## Message Stream

Message Stream shows every incident Hyper sent for the selected fixture.

### Message Stream Table

| Column     | Format      | Description                            |
| ---------- | ----------- | -------------------------------------- |
| Send Time  | HH:MM:SS:MS | When Hyper sent the message            |
| Incidents  | Icon + Text | Incident type with icon                |
| Values     | Varies      | Incident data (scores, players, stats) |
| Confidence | Percentage  | System confidence at send time         |
| Game Time  | MM:SS       | Match clock when incident occurred     |
| Period     | —           | Game phase the incident occurred in    |
| Message ID | #UUID       | Unique message identifier              |

### Cancelled Incidents

When an incident is cancelled after it was sent, it remains visible in the Message Stream for transparency — but is visually marked so it's immediately clear it is no longer valid.

**How cancelled incidents appear:**

* The entire row is grayed out — text, icons, and values are all dimmed
* A **Cancel** badge appears on the right side of the row

This applies consistently across all incident types (goals, fouls, cards, and others). No incidents are removed from the stream — cancelled ones stay visible so you have a full audit trail of everything that was sent.

![](/files/K6XoZmGotRJvpt4Qz5OU)

### Filters

| Filter     | Type        | Usage                   |
| ---------- | ----------- | ----------------------- |
| Message ID | Text search | Find specific message   |
| Incidents  | Dropdown    | Filter by incident type |
| Send time  | Sort        | Sort by timestamp       |
| Confidence | Dropdown    | Filter by confidence %  |

### Copy Message ID

Every message has a unique ID. Click directly on the Message ID in the rightmost column — it is automatically copied to clipboard.

**When to use Message ID:**

* Support tickets — reference specific messages
* Audits — track incidents in your systems
* Cross-referencing — match with backend logs
* Debugging — investigate discrepancies

### Download Message as JSON

Hover over any message row and click the download icon. The file saves as JSON to your device.

### Export to CSV

Available on both the Fixture screen and Message Stream screen. Click the **Download** button → a CSV file with all fixtures or incidents downloads to your computer.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lsports.eu/u/engage/hyper-livescore/hyper-livescore-tool.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
