Reference Data (Dictionaries API)

Dictionaries API

Host: dicts.api.breaking-bet.com

Dictionaries API returns a set of reference data necessary for correct interpretation and processing of data obtained from the main BreakingBet APIs. These dictionaries are used to decode identifiers, group markets, and match outcomes between bookmakers.

What Data Dictionaries API Provides

Bookmakers

Reference of all supported bookmakers.

• Format: id → bookmaker name
• Example: 7 → Pinnacle, 39 → Bet365, 31 → Betfair Ex
• Used in all API methods where bookmaker_id is present.

Additionally, a live_bookmakers array is returned — a list of bookmaker_id that support live lines.

---

Sports

Reference of sports types.

• Format: id → sport name
• Example: 1 → Football, 6 → Tennis, 5 → Basketball
• Used to filter events and markets by sport type.

---

Odds Groups

Reference of groups to which odds (markets) belong.

• Format: id → group name
• Examples:
  • Yellow Cards
  • 1 half
  • 3 period
  • Corners
  • 1 Map

---

Odds Sections (Market Sections)

Market classification.

• Format: id → section
• Examples:
  • main
  • handicaps
  • totals
  • itotals — individual totals
  • additional

Sections are used for UI, filtering, and market aggregation.

---

Odds Types

One of the key API references

• Format: odds_type_id → object
• Object fields:
  • title_short — short designation (e.g., TO, AH1, 1X)
  • title_full — full outcome description (e.g., Total Over)
  • lay — lay bet indicator (true / false)

Used for:

• bet type identification;
• matching equivalent markets between bookmakers;
• building arbs, middles, and value-bets.

---

Odds Types Reflections

Reference of reflections (mirror / reflection) between outcome types.

• Format: odds_type_id → reflected_odds_type_id
• Examples:
  • AH1 ↔ AH2
  • TO1 ↔ TO2
  • Score 1 Yes ↔ Score 2 Yes

Used for:

• automatic matching of first and second team outcomes;
• building symmetric markets;
• normalizing data between bookmakers.

---

Purpose of Dictionaries API

Dictionaries API is a core service that:

• decodes numeric identifiers into human-readable form;
• provides a unified dictionary for all API clients;

It is recommended to cache Dictionaries API responses on the client side and update them periodically (e.g., once every few hours).