spell-checkTerminology

LSports terminology, abbreviations, and domain concepts

This page provides standardized definitions for terms, abbreviations, and concepts used throughout ARENA360 documentation. Understanding these terms is essential for successful integration and operation.


Core Concepts

These are the fundamental building blocks of sports betting data:

Fixture

A contained sport gathering within the larger sport context — whether it's a direct head-to-head event or an entire league competition.

Example: Manchester United vs Liverpool, Kentucky Derby Race 5, NBA Finals Game 7

Livescore

An accompanying context which sheds light on the fixture's score, stats, lineups, and more. Livescore data is updated in real-time during InPlay.

Market

A "question" presented by a sportsbook to their end users regarding the fixture outputs — whether score-related, statistics, player-oriented, or even for the entire league's conclusions.

Example: "Who will win?" (1X2), "Will there be more than 2.5 goals?" (Over/Under)

Bet

The potential outcome for a suggested market. Each market contains one or more bets representing the possible answers.

Example: In a 1X2 market, the bets are: "1" (Home Win), "X" (Draw), "2" (Away Win)

Odds

A numeric representation of the sportsbook's probability for each bet to occur. Expressed in decimal format (e.g., 1.85, 2.50).

Formula: Probability = 1 / Odds (before margin)

Settlement

A unique message that guides sportsbooks on how to operate with bets placed by their end users, based on predefined logic that takes into consideration various aspects of the fixture (score, stats, player outputs, and more).

PreMatch

The framework in which all content (odds, metadata, etc.) is sent BEFORE the fixture starts. PreMatch data is typically available days or weeks in advance.

InPlay

The framework in which all content is sent DURING the fixture's execution. InPlay data updates in real-time as the event progresses.

Margin

The built-in cut for sportsbooks to ensure profit, as well as a self-safety measure. Also known as "overround," "vigorish," or "vig."

Example: True probability of 50% might be offered at odds of 1.90 instead of 2.00


ARENA360 Architecture Layers

ARENA360 is built on a three-layer architecture:

Collection Layer

The always-on intake engine of ARENA360. Captures sports data from multiple sources:

  • Computer Vision — Real-time data extraction using advanced CV

  • Web Scouting — Data acquisition based on web scouting and OSINT

  • Human Scouts — In-venue and TV scouting for validation

  • Partner Feeds — Premium feeds from trusted partners

Integrity Layer

Transforms raw feeds into trusted, sportsbook-grade data:

  • Mapping & Correlation — Correlates events across providers

  • Normalization Engine — Standardizes markets and statistics

  • Feature Extraction — Derives additional insights

  • Quality Controls — Automated validation and anomaly detection

ARENA360 Products Layer

The intelligence layer delivering value to sportsbook teams.


ARENA360 Products

TRADE — Sports Content Control & Markets Engine

The core odds feed product delivering real-time pre-match and in-play market data. TRADE provides configurable provider selection, margin settings, and settlement handling.

For: Head of Trading, Senior Trader, Live Betting Manager

DEFEND — Risk Management & Exposure Control

The centralized risk management system for monitoring betting activity, setting limits, and managing player risk across your sportsbook operations.

For: Head of Risk, Risk & Integrity Manager, Fraud Analyst

BOOST — Analytics & Insights

The provider performance analytics platform for coverage monitoring, provider benchmarking, and trading performance analysis.

For: Performance Analyst, BI Manager, Executive & Strategy Personnel

ENGAGE — Personalization & Recommendations

The player engagement suite including Tips Feed (betting recommendations) and Hyper Livescore (enhanced real-time match data and widgets).

For: Head of Marketing, CRM Manager, VIP Retention Manager


Fixture Statuses

Status
Abbreviation
Description

Not Started Yet

NSY

Fixture is in the pre-match phase

About to Start

ATS

Fixture is about to begin shortly

In Progress

IP

Fixture is live and currently in play

Finished

FIN

Fixture has ended and results are confirmed

Cancelled

CAN

Event will not take place

Postponed

PPD

Fixture is postponed; may return later

Interrupted

INT

Temporarily stopped; may resume

Abandoned

ABN

Permanently stopped; will not resume

Lost Coverage

LC

Coverage lost during live event


Market Types

1X2 (Three-Way)

The most common market for sports with draws. Bets on Home Win (1), Draw (X), or Away Win (2).

12 (Two-Way / Moneyline)

Market for sports without draws. Bets on Home Win (1) or Away Win (2).

Asian Handicap (AH)

A handicap market that eliminates the draw by giving one team a head start. Lines are expressed as decimals (e.g., -1.5, +0.5, -0.25).

Under/Over (U/O)

A market betting on whether a statistic (usually goals/points) will be above or below a specified line (e.g., Over 2.5 goals).

Outright

Long-term markets on competition results (e.g., league winner, top scorer, relegation).


Technical Abbreviations

Abbreviation
Full Term
Description

API

Application Programming Interface

HTTP endpoints for data retrieval and operations

RMQ

RabbitMQ

Message broker for real-time data streaming

SDK

Software Development Kit

Pre-built libraries for integration (.NET, Java, Node.js)

JWT

JSON Web Token

Authentication token format

SSO

Single Sign-On

Unified authentication across platforms

CSM

Customer Success Manager

Your dedicated LSports account contact

BPS

Benchmark Provider System

Provider comparison tool in BOOST

vhost

Virtual Host

Logical partition in RabbitMQ


Data Delivery Terms

Snapshot

A complete data export at a point in time. Used for initial synchronization when first connecting.

Delta Update

A message containing only changed data rather than a full snapshot. All RabbitMQ messages after initial snapshot are deltas.

Distribution

The data delivery service that must be enabled before consuming messages. Start/Stop via API.

Package

A subscription configuration defining which data (sports, leagues, markets) you receive.

Package ID

Unique numeric identifier for your subscription. Used in RabbitMQ queue names as _PACKAGE_ID_.


Odds & Pricing Terms

Calculated Odds

Odds processed through margin calculations, ready for display to end users.

Provider Odds

Raw odds from the data provider before any margin adjustments.

Provider Odds+

Feature providing access to original provider odds alongside calculated odds.

Mainline

The primary/central line in a market with multiple line options. Typically the most liquid.

Baseline

The reference point from which handicap and total lines are calculated.

Line

The specific handicap or total value in a market (e.g., 2.5 in "Over 2.5 Goals").


Settlement Terms

Win

Selection won; full payout to bettor.

Lose

Selection lost; stake forfeited.

Refund (Void)

Bet cancelled; stake returned to bettor.

Half Win

Partial win, typically in Asian Handicap or dead heat scenarios.

Half Lose

Partial loss, typically in Asian Handicap scenarios.

Dead Heat

Two or more selections tie; stakes divided equally among tied selections.


Connection Terms

Heartbeat

Periodic message confirming connection is active. Typically every 10 seconds.

Keep Alive

Message to maintain connection during low activity periods.

Safe Message

Feature ensuring guaranteed message delivery without data loss.

Suspension

When odds are temporarily unavailable for betting, typically during active play or uncertain situations.


Entity Types

Participant

A team, player, or competitor in a fixture. Position 1 = Home, Position 2 = Away.

Provider

A source of odds or data (e.g., Bet365, Pinnacle, Betfair).

Competition / League

A series of fixtures within a sport (e.g., Premier League, NBA, Roland Garros).

Location

Country or region where a competition takes place.

Sport

The category of athletic activity (e.g., Football, Basketball, Tennis).


Platform Terms

Trading Floor

The TRADE monitoring interface for real-time fixture management during pre-match and in-play.

Coverage Hub

BOOST feature for analyzing provider coverage across sports, leagues, and markets.

Tips Feed

ENGAGE service delivering betting recommendations via RabbitMQ.

Hyper Livescore

ENGAGE real-time score and incident service with embeddable widgets.


Common ID Formats

ID Type
Format
Example

Fixture ID

Integer

12345678

Market ID

Integer

1 (1X2), 2 (U/O)

Bet ID

Integer

11287986013115994

Provider ID

Integer

8 (Bet365)

Sport ID

Integer

6046 (Football)

Location ID

Integer

250 (England)

League ID

Integer

1001


Timestamp Format

All timestamps in ARENA360 use UTC in ISO-8601 format:


See Also

Last updated

Was this helpful?