> For the complete documentation index, see [llms.txt](https://docs.feedb2b.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feedb2b.com/reference/glossary.md). # Glossary This glossary defines the key terms used throughout the FeedB2B platform, API, and documentation. ### Provider An external sports data and odds provider integrated with FeedB2B. FeedB2B connects multiple providers and exposes their data through a unified integration, allowing clients to access different providers without implementing each provider's API separately. ### Provider ID A unique identifier used by FeedB2B to identify a provider. Provider IDs are used throughout the API to identify the provider from which particular data originates. ### Sport The top-level classification of a sporting event, such as Football, Tennis, Basketball, Ice Hockey, or Volleyball. ### Competition A league, tournament, cup, or other organized competition in which events take place. Examples include the Premier League, UEFA Champions League, ATP tournaments, and NBA. ### Event A sporting event available through FeedB2B. An event usually represents a match or game between two or more participants. Examples: * Arsenal vs Chelsea * Real Madrid vs Barcelona * Player A vs Player B An event may contain information such as the sport, competition, participants, scheduled start time, status, markets, and other event-related data. Some providers may use the term **fixture** for the same concept. Within FeedB2B, the standard term is **Event**. FeedB2B maps corresponding events from different providers so that the same real-world event can be identified across multiple providers. ### Participant A team, player, or other competitor taking part in an event. Depending on the sport, an event may contain two or more participants. ### Prematch Data provided before an event starts. Prematch data may include event information, markets, bets, odds, and other information available before the event becomes live. ### Live Data provided while an event is in progress. Live data can change frequently as the event progresses and may include odds, markets, scores, statistics, and other event information. ### Market A betting category that defines what customers can bet on within an event. Examples: * 1X2 * Total Goals * Both Teams to Score * Correct Score * Handicap * Next Goal A market contains one or more bets. ### Market Type The standardized FeedB2B definition of a market. Different providers may use different names and identifiers for equivalent markets. FeedB2B maps provider-specific markets to common FeedB2B market types. For example, provider markets named **Match Result**, **Full Time Result**, and **1X2** may all correspond to the same FeedB2B market type. ### Type The outcome structure of a market type: which bet names it can have and whether its bets carry a line. For example, `1_x_2` means the bets are **Home**, **Draw**, and **Away**; `over_under` means **Over** and **Under** with a line. ### Base Market Type The question a market asks, such as **Winner**, **Total**, **Handicap**, or **First to Score**. It is independent of the type, period, incident type, and team. For example, **Match Result** and **Double Chance** are both **Winner** markets with different types, and **Total Goals Over/Under** and **Total Corners Odd/Even** are both **Total** markets. See [Event Details](https://docs.feedb2b.com/platform/event-details.md#type-and-base-market-type) for the full list. ### Bet A selectable option within a market. For example, for the **1X2** market, the bets are typically: * Home * Draw * Away For a **Total Goals** market, bets may include: * Over 2.5 * Under 2.5 A bet may contain a line when an additional value is required to fully define the betting option. ### Bet Name The standardized name used to identify a bet within a market. Providers may use different names for equivalent bets. FeedB2B maps provider-specific bet names into a consistent structure. For example, **Home**, **Team 1**, and **1** from different providers may be mapped to the same FeedB2B bet name. ### Line A **Line** is a value used to further define a bet within a market. The line is associated with the **bet name**. For example, for the **Total Goals** market: * Over 1.5 / Under 1.5 * Over 2.5 / Under 2.5 * Over 3.5 / Under 3.5 Here, **1.5**, **2.5**, and **3.5** are lines. Lines are commonly used in markets such as Totals and Handicaps, where the same bet name can be offered with different values. For example: **Market:** Total Goals\ **Bet Name:** Over\ **Line:** 2.5 Together, the bet name and line represent **Over 2.5**. ### Specifier A **Specifier** is a parameter that provides additional information required to identify a particular variation of a market. Unlike a line, which adds a value to the bet name, a specifier provides a dynamic value associated with the **market name or definition**. #### Example: Time Range Market: **Total Goals 10 min (X–Y)** Specifiers: `from=00:00`\ `to=10:00` The specifiers define the time interval represented by **X–Y** in the market name. Another instance of the same market may have: `from=10:00`\ `to=20:00` This allows the same market type to represent different time intervals without creating a separate market type for every interval. #### Example: Goal Number Market: **Next Goal** Bets: * Home * Away * None Specifier: `goalnr=2` In this case, the specifier indicates that the market refers to the **2nd goal**. The same market type can therefore be used with different `goalnr` values while maintaining the same market structure. ### Line vs Specifier Lines and specifiers represent different concepts in FeedB2B. A **Line** adds a dynamic value to the **bet name**. For example: **Market:** Total Goals\ **Bet Name:** Over\ **Line:** 2.5\ **Displayed Bet:** Over 2.5 A **Specifier** adds dynamic information to the **market**. For example: **Market:** Total Goals 10 min (X–Y)\ **Specifier:** `from=00:00, to=10:00` Or: **Market:** Next Goal\ **Specifier:** `goalnr=2` Keeping lines and specifiers separate is important when mapping markets and bets across different providers. ### Odds The price associated with a bet. Odds may change throughout the lifetime of a market, particularly for Live events. ### Settlement The final result assigned to a bet after the relevant outcome has been determined. Settlement information is received from providers and mapped by FeedB2B into a unified settlement structure. Common settlement values include: * Win * Lose * Void * Half Win * Half Lose ### Mapping The process of identifying equivalent data from different providers and connecting it to a common FeedB2B representation. FeedB2B performs mapping at multiple levels, including: * Events * Markets * Bet names * Settlements Mapping reduces the amount of provider-specific logic required on the client side. ### Event Mapping The process of identifying events from different providers that represent the same real-world sporting event. Once mapped, corresponding provider events are connected to the same FeedB2B event. This makes it easier to use, compare, or switch between different providers. ### Market Mapping The process of mapping provider-specific markets to common FeedB2B market types. Providers may use different names, IDs, or structures for the same betting concept. Market mapping allows these differences to be represented through a consistent FeedB2B structure. ### Bet Name Mapping The process of mapping provider-specific bet names to standardized FeedB2B bet names. For example, different providers may represent the home selection as **Home**, **Team 1**, or **1**. FeedB2B can map these values to the same standardized bet name. Lines remain separate from the mapped bet name. For example: **Bet Name:** Over\ **Line:** 2.5 rather than treating **Over 2.5** as a completely different bet name from **Over 3.5**. ### Settlement Mapping The process of converting provider-specific settlement values into the common settlement values used by FeedB2B. This allows clients to process settlements consistently across multiple providers. ### Subscription A request to receive data for a specific event from a selected provider. Once subscribed, the client receives relevant updates for that event according to the available provider data and FeedB2B API. ### Event Update A change related to an event received while the event is being monitored. Updates may include changes to: * Event information * Scores * Statistics * Markets * Bets * Odds * Settlements * Other provider data ### API Application Programming Interface. The FeedB2B API is the technical interface through which clients connect to the platform, retrieve data, subscribe to events, and receive updates. ### Client A company or platform integrated with FeedB2B and consuming data through the FeedB2B API. ### Feed The stream of sports and betting data delivered through FeedB2B. Depending on the provider and client configuration, the feed may contain event information, markets, bets, odds, statistics, settlements, and other updates.