Reference Data (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 BreakingBet main APIs. These dictionaries are used to decode identifiers, group markets, and match outcomes between bookmakers.
What Data Does Dictionaries API Provide
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_idis present.
Additionally, a live_bookmakers array is returned — a list of bookmaker_id values 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:
main— main outcomestotals— totalshandicaps— handicapsadditional— additional markets- periods, halves, cards, corners, sets, rounds, etc.
Used for logical grouping of markets within an event.
Odds Sections
Higher-level market classification.
- Format:
id → section - Examples:
mainhandicapstotalsitotals— individual totalsadditional
Sections are applied 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 descriptionlay— 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 ↔ AH2TO1 ↔ TO2Score 1 Yes ↔ Score 2 Yes
Used for:
- automatic matching of first and second team outcomes;
- building symmetric markets;
- data normalization between bookmakers.
Purpose of Dictionaries API
Dictionaries API is a basic service that:
- decodes numeric identifiers into human-readable form;
- provides a unified dictionary for all API clients;
- is used when working with:
- Events API
- Odds API
- Arbitrage / Valuebets API
- Analytics and Historical Data API
Caching
It is recommended to cache the Dictionaries API response on the client side and update it periodically (e.g., once every few hours).