MQTT JSON Contracts

This section contains the JSON payload contracts published on MQTT json topics. This section documents the Sportzcast JSON payload contracts for client-facing integrations.

Quick Navigation

• Shared base contract (applies to every sport payload): Sport
• Base + sport extension index: Sports Contracts Reference
• Sport-specific extension contracts (with property types and examples):
  • BaseballSoftball
  • Basketball
  • DragRacing
  • Football
  • FutsalHandball
  • Generic
  • HockeyLacrosse
  • Rodeo
  • Soccer
  • SwimmingDetail
  • SwimmingEvent
  • SwimmingMixed
  • SwimmingRows
  • TableTennisBadminton
  • Tennis
  • Timer
  • Volleyball
  • WaterPolo
  • Wrestling

Scope

• Includes concrete contracts that inherit from Sport.
• Focuses on consumer-facing payload contracts used by client integrations.
• Lists public, consumer-facing members, their data types, and example values.

Contract inheritance model

All MQTT JSON sport payloads follow the same model:

1. Shared base fields from Sport (clock/origin/timestamps/bot/team metadata)
2. Additional sport-specific fields (for example Basketball, Soccer, Volleyball, etc.)

In practical terms, every sport contract is Sport base + sport extension fields.

MQTT context

• These contracts apply when subscribing to bot/{botNumber}/json.
• Contract shape varies by decoded sport (EventId / vendor sport mapping).
• See MQTT integration guide: MQTT: Get Data from a Scorelink.