SportLive

ExeFeed Odds Feed

Live odds and a full sports catalog from ExeFeed, normalised and delivered as one clean stream.

Take the ExeFeed live-odds feed exactly as the provider publishes it, and receive it as one

normalised stream you can build a sportsbook on — without writing a line of provider-specific

parsing, and without running the ingest yourself.

What you get

  • Live odds, as they move. Every price change on every offered market, pushed the moment the

provider sends it — not polled, not batched.

  • A complete catalog. Sports, categories, competitions, fixtures, markets and outcomes, with

stable identifiers, kept current as the provider's own catalog changes.

  • Bet stops and suspensions, honoured. When a market is taken off, you are told — the single

most expensive thing to get wrong in a live book.

  • One shape for everything. Odds and catalog arrive in our canonical format, the same one every

other SportLive feed uses. Add a second provider later and nothing downstream changes.

  • Nothing is guessed. Every line the provider sends is archived verbatim before we touch it, so

anything we could not map is recoverable rather than silently dropped.

How it is delivered

We run it. The feed is a hosted service on SportLive infrastructure: we hold the provider session,

absorb its reconnects and its catalog reloads, and hand you a stream that stays up. You consume it

over a private link — there is no public port and no shared endpoint.

Delivery is per customer. You get your own instance, your own credentials and your own coverage

scope (the sports and competitions you actually sell), and a rolling archive of the raw provider

traffic behind it.

What it needs from you

A live ExeFeed entitlement of your own, or ours — we can arrange either. Tell us which sports and

competitions you want, and where you want the stream delivered.

Getting started

Use Request access below. We will come back with coverage, a delivery shape and a price.

Pull it from the SportLive registry

This package ships as a container image:

docker login registry.sportlive.hr
docker pull registry.sportlive.hr/betpipeline/exefeed-mapper:main

Registry credentials come with the contract — ask for them with your access request (Request access) and we issue a pull-only account for your deployment.

In a betpipeline deployment, bp register registry.sportlive.hr/betpipeline/exefeed-mapper:main writes the package into the cluster's installed-package inventory (bp_framework.plugin_registry, which the portal reads live), and the image then runs as one more service in the stack's compose file — docker compose up -d on the box, exactly like a first-party vertex.