Half-Time League Average

Reference for HT league_average developer types — naming convention, value semantics, how they differ from full-time averages, and usage with /fixtures/search.

Half-Time League Average Types

GET /types?developer_type=league_average

Half-time league average types represent per-match averages calculated from the first half only, across all fixtures played in a league season. They are identified by the HT_ prefix and follow the same storage and filtering rules as full-time league averages.


Naming Convention

Every half-time developer_name follows a four-part pattern:

HT_{SCOPE}_{METRIC}_{AGGREGATION}
PartValuesMeaning
HT(fixed)Marks the value as a first-half average
SCOPEHOMEAverage from home team first-half performances only
AWAYAverage from away team first-half performances only
OVERALLCombined average: (HOME + AWAY) / 2
METRICGOALS, CORNERS, YELLOWCARDS, SHOTS_ON_TARGET, SHOTS_OFF_TARGET, ATTACKS, DANGEROUS_ATTACKSThe measured statistic
AGGREGATIONSCOREDAverage number of events that occurred per match in the first half

Examples:

developer_nameMeaning
HT_HOME_GOALS_SCOREDAverage first-half goals scored by the home team per match
HT_AWAY_CORNERS_SCOREDAverage first-half corners taken by the away team per match
HT_OVERALL_YELLOWCARDS_SCOREDAverage first-half yellow cards per side per match (HOME + AWAY) / 2

Full Type Reference

type_iddeveloper_nameScopeMetric
324HT_HOME_GOALS_SCOREDHomeGoals
325HT_AWAY_GOALS_SCOREDAwayGoals
326HT_OVERALL_GOALS_SCOREDOverallGoals
327HT_HOME_CORNERS_SCOREDHomeCorners
328HT_AWAY_CORNERS_SCOREDAwayCorners
329HT_OVERALL_CORNERS_SCOREDOverallCorners
330HT_HOME_YELLOWCARDS_SCOREDHomeYellow Cards
331HT_AWAY_YELLOWCARDS_SCOREDAwayYellow Cards
332HT_OVERALL_YELLOWCARDS_SCOREDOverallYellow Cards
333HT_HOME_ATTACKS_SCOREDHomeAttacks
334HT_AWAY_ATTACKS_SCOREDAwayAttacks
335HT_OVERALL_ATTACKS_SCOREDOverallAttacks
336HT_HOME_SHOTS_ON_TARGET_SCOREDHomeShots on Target
337HT_AWAY_SHOTS_ON_TARGET_SCOREDAwayShots on Target
338HT_OVERALL_SHOTS_ON_TARGET_SCOREDOverallShots on Target
339HT_HOME_SHOTS_OFF_TARGET_SCOREDHomeShots off Target
340HT_AWAY_SHOTS_OFF_TARGET_SCOREDAwayShots off Target
341HT_OVERALL_SHOTS_OFF_TARGET_SCOREDOverallShots off Target
342HT_HOME_DANGEROUS_ATTACKS_SCOREDHomeDangerous Attacks
343HT_AWAY_DANGEROUS_ATTACKS_SCOREDAwayDangerous Attacks
344HT_OVERALL_DANGEROUS_ATTACKS_SCOREDOverallDangerous Attacks

Values and the /fixtures/search Endpoint

How values are stored

All half-time average values are stored as integers scaled by 1000, identical to full-time averages.

Stored valueReal-world average
5000.5 per first half
8000.8 per first half
12001.2 per first half

The OVERALL ÷ 2 rule

HT_OVERALL_* values equal (HT_HOME + HT_AWAY) / 2. They represent the average contribution per side, not the full first-half match total. The same rule as full-time OVERALL_* applies.

When filtering by first-half match total, divide your target by 2.

Example — find leagues averaging 1.0 total first-half goals per match:

1.0 / 2 = 0.5 per side → HT_OVERALL_GOALS_SCORED stored as 500.

GET /fixtures/search?where[HT_OVERALL_GOALS_SCORED]=500:9999

HOME and AWAY filters

HT_HOME_* and HT_AWAY_* values represent a single side's contribution and require no halving.

# Leagues where home teams average more than 0.8 first-half goals
GET /fixtures/search?where[HT_HOME_GOALS_SCORED]=800:9999

# Leagues where away teams average fewer than 3 first-half corners
GET /fixtures/search?where[HT_AWAY_CORNERS_SCORED]=0:2999

Differences from Full-Time Averages

AspectFull-time (*_SCORED)Half-time (HT_*_SCORED)
Period coveredEntire matchFirst half only
type_id range303–323324–344
Typical goals value~1.2–1.6 per side~0.5–0.8 per side
Typical corners value~4–6 per side~2–3 per side
Developer name prefix(none)HT_
Calculation sourcefixture_trends (full match)fixture_trends joined with periods.type_id = 1

Practical Use Cases

1. Find high first-half scoring leagues

Target leagues where first-half goals are likely, useful for HT result markets.

GET /fixtures/search?window=48
  &where[HT_OVERALL_GOALS_SCORED]=600:9999
  &include=odds

2. Find leagues with active first-half corner markets

GET /fixtures/search?window=24
  &where[HT_OVERALL_CORNERS_SCORED]=2500:9999
  &status=NOT_STARTED

3. Compare first-half vs full-time goal rates

Fetch both HT_HOME_GOALS_SCORED (type 324) and HOME_GOALS_SCORED (type 303) together to compute the first-half scoring ratio for each league.

GET /fixtures?league_id=8&include=metrics
  &filter[metrics]=types:303,304,324,325

A ratio above ~0.55 means the league tends to produce goals early — valuable for live betting models.


UI Implementation Notes

  • Display values: Divide stored integer by 1000 (800 → 0.8).
  • Labels: Prefix the metric name with "HT" or "1st Half" in the UI to distinguish from full-time figures.
  • OVERALL filter inputs: When accepting a "first-half total" from the user (e.g. "1.0 goals"), divide by 2 before sending (1.0 → 0.5 → 500 in API units).
  • HOME/AWAY filter inputs: Divide by 1000 only — no halving required.
  • Range sliders: Scale by 1000. A reasonable UI range for first-half goals is 0–2.0 per side (0–2000 in API units).