---
title: "Discussion on \"How Orbistats Normalizes Odds Across Bookmakers: A Technical Breakdown\" | Hashnode"
description: "Discussion on \"How Orbistats Normalizes Odds Across Bookmakers: A Technical Breakdown\". A technical deep dive into normalizing sports betting odds: event matching, market mapping, devigging, Asian handicaps and delivery over REST and WebS"
url: "https://hashnode.com/posts/how-orbistats-normalizes-odds-across-bookmakers-a-technical-breakdown/6ac3a557b60a172b1f2a3df5"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How Orbistats Normalizes Odds Across Bookmakers: A Technical Breakdown](https://bettechmagnetics.hashnode.dev/how-orbistats-normalizes-odds-across-bookmakers-a-technical-breakdown?utm_source=hashnode&utm_medium=feed)

A technical deep dive into normalizing sports betting odds: event matching, market mapping, devigging, Asian handicaps and delivery over REST and WebS

Oct 5 · 17 min read · bettechmagnetics.hashnode.dev  
Read the article

-   [#odds-api](https://hashnode.com/tag/odds-api)
-   [#api-design](https://hashnode.com/tag/api-design)
-   [#data-engineering](https://hashnode.com/tag/data-engineering)
-   [#sports-data](https://hashnode.com/tag/sports-data)
-   [#backend](https://hashnode.com/tag/backend)

## Written by

[Vijay Choudhary](https://hashnode.com/@orbistats)

@orbistats · United Kingdom

  
[View profile](https://hashnode.com/@orbistats)

Building sports data APIs at Orbistats

I write about backend architecture, API design, and building data platforms that need to stay consistent across structurally different domains. Currently building Orbistats — a sports data and odds API covering 11 mainstream sports. I share lessons from designing schemas that hold up across football, cricket, tennis, basketball and more, where the "same" problem is never actually the same problem twice. Topics I write about: - API design &amp; versioning - Multi-domain schema architecture - Sports data &amp; real-time feeds - Developer experience for data products Always happy to talk about schema design, backend systems, or where a unified data model actually breaks in production.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
