Introduction

WagerKit is a real-time integrity monitoring and odds aggregation platform designed for modern betting operators.

What is WagerKit?

WagerKit provides a unified API to access odds from multiple providers, monitor market movements in real-time, and detect integrity issues. It acts as a middleware layer that standardizes data formats and provides powerful tools for risk management.

Key Features

Real-time odds aggregation from 50+ sources
Automated integrity monitoring and alerts
Unified API for all sports and markets
WebSocket streams for live updates

Quick Start

Get up and running with WagerKit in minutes. Install our SDK or use the REST API directly.

Terminal

bash

npm install @wagerkit/sdk

Architecture

WagerKit is built on a high-performance, event-driven architecture designed to handle thousands of odds updates per second with sub-second latency.

Ingestion Layer

Distributed collectors fetch data from 50+ sources including on-chain oracles and traditional sportsbooks. Data is normalized and pushed to our message queue.

Integrity Engine

Real-time stream processors analyze odds movements to detect anomalies, arbitrage opportunities, and potential match-fixing signals.

Integration

Integrating WagerKit into your backend is straightforward. We recommend using our official SDKs for the best experience.

1. Initialize the Client

src/lib/wagerkit.ts

typescript

import { WagerKit } from '@wagerkit/sdk';
const client = new WagerKit({
  apiKey: process.env.WAGERKIT_API_KEY,
});
// Fetch active markets
const markets = await client.markets.list({
  limit: 10,
  sport: 'soccer'
});

Webhooks

Listen for real-time updates using webhooks. We'll send a POST request to your configured URL whenever an event occurs.

Note: You must verify the webhook signature to ensure the request came from WagerKit.

Example Payload

Webhook Payload

json

{
  "id": "evt_123456",
  "type": "odds.update",
  "created_at": 1732180000,
  "data": {
    "market_id": "mkt_abc123",
    "source": "bet365",
    "odds": {
      "home": 1.95,
      "away": 3.40,
      "draw": 3.60
    }
  }
}

Best Practices

Cache ResponsesMarket data doesn't change every millisecond. Cache API responses for at least 30 seconds to reduce latency and API usage.
Handle Rate LimitsRespect the X-RateLimit-Remaining header. Implement exponential backoff if you hit a 429 error.
Verify WebhooksAlways verify the WagerKit-Signature header to prevent replay attacks and ensure data authenticity.