Fancy and Bookmaker API Explained: What It Is, How It Works, Types & Best Provider Guide

A Fancy API and a Bookmaker API serve two distinct but complementary purposes in the sports betting ecosystem. While a Bookmaker API provides the odds and market structures that define what bets are available, a Fancy API delivers the micro-event data needed to power exotic, high-frequency betting markets. This guide explains what each API type is, how they work, the key differences between them, and how to choose the right provider for your sportsbook.

Understanding Bookmaker API and its Core Features

A Bookmaker API is an interface that allows a betting platform to retrieve odds, market data, and event information from a bookmaker or odds provider. Think of it as the “price feed” for sports betting. It offers the core features:

• Odds Retrieval: The primary function is fetching pre-match and live odds for thousands of events across multiple sports. These odds come in various formats, decimal, fractional, or American, depending on the market.
• Market Structure: Bookmaker APIs deliver information about which betting markets are available for a given event. For a football match, this includes match winner, over/under goals, both teams to score, correct score, and dozens of other markets.
• Event Metadata: Beyond odds, these APIs provide fixture information: team lineups, venue details, start times, and weather conditions that might affect play.
• Historical Data: Many bookmaker APIs offer access to historical odds, allowing operators to analyse past price movements and settlement results. This is crucial for auditing and risk management.

How Does a Bookmaker API Work?

The technical flow of a Bookmaker API follows a request-response model with real-time streaming capabilities.

Authentication: Most bookmaker APIs require an API key or similar credential passed as a query parameter with every request. This identifies the operator and tracks usage for billing.

Data Retrieval: The API provides multiple endpoints for different data types. Common endpoints include:

• `/sports` – Lists available sports and leagues
• `/odds` – Returns odds for current events
• `/scores` – Provides live and completed scores
• `/events` – Delivers event-specific metadata 

Odds Calculation: Behind the scenes, the bookmaker’s pricing engine calculates probabilities based on statistical models, historical data, and real-time market movements. These calculations are converted into odds and pushed through the API.

Real-Time Updates: For live betting, Bookmaker APIs use WebSocket connections to push odds updates continuously. When a team scores, odds for the “next goal” or “match winner” markets change within milliseconds.

Settlement: After an event concludes, the API provides settlement data, which shows outcomes won and at what odds. Some APIs include automated payout calculations.

Types of Bookmaker APIs

1. Premium Odds APIs: These provide high-quality, vetted odds from established bookmakers. They include historical data and multiple odds formats. The trade-off is a higher cost.
2. Aggregator APIs: These combine odds from multiple bookmakers into a single feed. Operators can compare prices across sources to offer the best available odds to their users.
3. Trading APIs: Designed for operators who manage their own risk, these APIs allow for manual odds adjustment. A trader can raise or lower odds on specific markets through API calls, which then push updates to the frontend.
4. Settlement APIs: Focused on post-match processing, these APIs deliver official results and automated settlement instructions. They integrate directly with sportsbook wallet systems.

Understanding Fancy API and its core features

A fancy API (also known as a “fancy bet” or “scripted betting” API) powers non-traditional, high-frequency betting markets. Unlike standard APIs that focus on match outcomes, Fancy APIs break matches down into micro-events. The term “fancy” comes from these being exotic betting options, things like “runs scored in the next over” for cricket or “next point winner” for tennis. It offers the core functionalities:

• Micro-Event Tracking: Fancy APIs track every ball, point, or play within a match. For cricket, this means each delivery: runs scored, wicket status, and extras.
• Dynamic Market Creation: These APIs create and close markets on the fly. When a new batter comes to the crease, a “Batsman Runs” market opens automatically. When a wicket falls, that market closes instantly.
• Suspension Management: Fancy APIs send “suspend” signals during critical moments, like a wicket falling or a boundary being hit, to prevent bettors from exploiting data delays.
• Session Management: For longer-term fancy markets like “session runs” (runs scored in overs 1-6), the API manages the entire lifecycle from market opening to settlement.

How does a fancy API work?

The technical requirements for Fancy APIs are more demanding than standard Bookmaker APIs due to the speed and volume of data.

Real-Time Data Collection

Data is collected either through manual feeders (humans watching matches and logging events) or computer vision systems that detect events automatically. Dual-source systems use two independent feeders for redundancy.

Event Normalization

Raw event data is converted into structured betting events. For example, a “four runs” signal from a cricket match is normalized into a betting outcome that can trigger market settlement.

Market State Management

The API maintains the state of every active fancy market. For a “Next Over Runs” market, the API tracks:

• Current over number
• Balls bowled in the current over
• Current market status (open/suspended)
• Current odds

Continuous Push Updates

Unlike Bookmaker APIs that can tolerate brief polling intervals, Fancy APIs use persistent WebSocket connections. Data pushes every 100-500 milliseconds to ensure micro-event timing accuracy.

Automated Settlement

When a micro-event completes, a wicket falls, a goal is scored, the API immediately settles all related fancy markets and sends the results to the operator’s wallet system.

Types of Fancy APIs

1. Cricket-First Fancy APIs

Cricket is the primary market for fancy betting. These APIs specialize in ball-by-ball data, session markets (overs 1-6, 7-12, etc.), player performance bets, and method of dismissal markets.

2. Multi-Sport Fancy APIs

Some providers offer fancy markets across football, tennis, basketball, and other sports. Football fancy markets include “next goal time,” “cards in the next 10 minutes,” and “corners race.”

3. Player Prop APIs

Focused specifically on individual player performance: runs scored, wickets taken, shots on goal, three-pointers made. These APIs integrate with daily fantasy sports platforms as well as traditional sportsbooks.

4. Trading-First Fancy APIs

Designed for operators who manage their own risk on fancy markets, these APIs include back-office tools for setting lines, adjusting odds manually, and monitoring exposure in real-time.

Bookmaker API vs. Fancy API: Key Differences between Both

Aspect	Bookmaker API	Fancy API
Primary Purpose	Deliver odds and market structures	Deliver micro-event data
Data Frequency	Updates every few seconds	Updates every 100–500 milliseconds
Market Types	Match winner, over/under, handicaps	Runs per over, next wicket, player props
Settlement	Post-match	Real-time, often ball-by-ball
Latency Tolerance	2–3 seconds acceptable	Sub-second required
Primary Sport	All sports	Cricket, tennis, football (secondary)
Technical Protocol	REST + WebSockets	WebSockets (continuous stream)
User Base	Pre-match and live bettors	High-frequency, in-play traders

How to Choose the Best Facny an Bookmaker API Provider

For Bookmaker APIs

1. Verify Odds Depth and Coverage

A provider might claim coverage of 100 sports, but their depth matters more. Check whether they offer all standard markets for your priority sports, do they have Asian handicaps, correct score, both teams to score, and player props for football? 

2. Check Historical Data Access

Premium Bookmaker APIs provide historical odds for up to seven days after an event concludes. This is essential for auditing, customer dispute resolution, and building trading models.

3. Evaluate Multiple Bookmaker Sources

Aggregator APIs that pull from 70+ bookmakers allow you to offer competitive odds by displaying the best price available. Single-source APIs limit your pricing flexibility.

4. Test Real-Time Performance

During peak hours, Saturday afternoons with multiple football leagues playing simultaneously, latency often increases. Request a test key and monitor update speeds during live events.

5. Examine Settlement Automation

Does the API automatically settle winning bets, or does it simply deliver results while your system handles settlement? Full automation reduces operational overhead and eliminates manual errors.

For Fancy APIs

1. Demand Dual-Source Data

Fancy markets rely on human data feeders. If one feeder experiences lag, a second source provides backup. Providers without redundancy will lose data during critical moments.

2. Test Suspension Speed

When a wicket falls in cricket, the “Next Ball Runs” market must suspend instantly, within 500 milliseconds. Slow suspension allows arbitrage bettors to place bets after the event has occurred but before the market closes.

3. Verify Secondary League Coverage

Every provider covers the Indian Premier League or the World Cup. The test is coverage for county cricket, Bangladesh Premier League, or women’s international matches. If fancy markets are unavailable for minor leagues, your users will notice.

4. Understand Dead Heat Rules

Fancy markets have complex settlement rules. For “Top Bowler” markets, if two bowlers take three wickets each, does the API return half stakes (Dead Heat) or apply a tiebreaker? Your provider must handle this automatically.

5. Request Sandbox with Historical Replay

A proper Fancy API sandbox should replay recorded matches. This allows you to test how the API behaves during high-pressure moments, wicket falls, reviews, rain delays, without risking live money.

Summary

A Bookmaker API and a Fancy API serve different layers of the sports betting stack. The Bookmaker API defines what bets are available and at what price. The Fancy API powers the high-frequency, ball-by-ball markets that keep users engaged during live events. For most operators, the question is not which API to choose, but how to integrate both effectively. A complete sportsbook requires the structural depth of a Bookmaker API and the real-time precision of a Fancy API, working together seamlessly. Power your sportsbook with fast, reliable, and real-time betting APIs from iGamiq that is a trusted solutions for Bookmaker, Fancy, Odds, and Live Betting integrations.

Frequently Asked Questions