Betting Engine Documentation

Welcome to the Betting Engine API documentation. This documentation covers the three-service architecture that powers the sports betting platform: Feedbird (program-engine), Betbird (betting-engine), and Databird (account-management).

Architecture Overview

The sportsbook platform consists of three specialized services using a webhook-based architecture:

Feedbird (Program Engine)

• Pushes program data via webhooks to Databird webhook endpoints
• Also exposes direct GET endpoints for other consumers (not used by frontend)
• Generates real-time and scheduled sports events, competitions, and markets data
• Handles navigation trees, live events, recommended events, and competition data
• Focuses on sports data, odds, and market information

Betbird (Betting Engine)

• Provides bet placement APIs (virtual ticket endpoints)
• Handles bet construction and validation logic
• Processes betting ticket creation and management

Databird (Account Management)

• Receives webhooks from Feedbird and aggregates program data
• Provides program endpoints (GET requests) to the frontend
• Handles all account management operations
• Manages user authentication and registration
• Processes deposits and withdrawals
• Performs transaction processing and history
• Executes pre-bet checks (balance verification, betting limits, account status)
• Acts as a proxy/gateway for bet placement requests to Betbird

Request Flow

Program Data Flow

Feedbird → Databird (webhooks)
Frontend → Databird (GET endpoints)

Feedbird pushes program data updates to Databird via webhooks. The frontend retrieves program data by polling GET endpoints from Databird (not directly from Feedbird).

Bet Placement Requests (POST)

Frontend → Databird → Betbird (proxied)

All bet placement requests flow through Databird, which performs authentication and pre-bet checks before proxying to Betbird.

Account Management Requests (POST)

Frontend → Databird (direct)

Account management operations (deposits, withdrawals, authentication) are handled directly by Databird.

Important: The frontend only communicates with Databird. There is no direct communication between the frontend and Feedbird or Betbird.

Getting Started