Data product · add-on
Relay Alerts — push, don't poll
Relay Alerts turns the matched feed push-first: instead of your app polling for opportunities, qualifying matched events are pushed to your endpoint over webhooks, filtered to the criteria you set. It's the difference between your users hearing about a tight pair as it appears and finding it on their next refresh. Alerts is an add-on to the matched feed, gated behind an active key.Powers a leading UK matched-betting platform.
$ curl api.oddsrelay.io/v1/odds/standard?region=uk \
-H "Authorization: Bearer or_live_••••••••••••"GET 200 · application/json
{
"event": "Arsenal v Chelsea",
"sport": "football",
"region": "uk",
"market": "match_odds",
"selection": "Arsenal",
"back": { book: "bet365", odds: 2.1 },
"lay": { exchange: "exchange", odds: 2.12 },
"rating": 98.1,
"updated_at": "2026-07-01T14:08:22Z"
}What it pushes, and when
When an opportunity crosses the thresholds you've configured — a rating band, a market, a book, a feed type — Relay Alerts posts a compact event to your webhook endpoint. The payload carries the same processed fields as a matched-feed row, so your handler renders or forwards it without a second lookup. You decide what qualifies; we deliver the ones that do.
Filtering is per-client, so a matched-betting platform and an arbitrage tool subscribed to the same feed receive different streams tuned to their users. The feed types you're licensed for define what alerts can fire on — standard pairs, dutching opportunities, racing offers, and so on.
Why push instead of poll
Polling is fine for a dashboard a user is already looking at; it's the wrong shape for notifying users who aren't. Building a reliable push layer yourself means running a differ, a queue and a delivery-retry story on top of the feed — infrastructure that has nothing to do with your product's value. Relay Alerts is that layer, delivered: you point it at an endpoint and handle events, rather than owning the plumbing.
It sits cleanly alongside the pull feed — most platforms use the matched feed for their on-screen oddsmatcher and Alerts for notifications, email or in-app pushes. One licence, two delivery modes.
What you get
Webhook-first delivery
Qualifying events POST to your endpoint as they appear — no polling loop, differ or queue for you to build.
Per-client filters
Subscribe by rating band, market, book or feed type, so each client's stream matches its users.
Matched-feed payloads
Events carry the same processed fields as a feed row — render or forward without a second lookup.
Gated behind your key
Alerts is an add-on to the matched feed, tied to an active key and the feed types you're licensed for.
An honest note
Relay Alerts is an add-on to the matched feed, not a standalone product — it requires an active feed key and fires only on the feed types you're licensed for. It's pre-match, matching the feed's cadence, and delivers over webhooks to an endpoint you host. Volume depends entirely on the filters you set.
Questions
What is Relay Alerts?
A webhook push add-on to the matched feed. Instead of your app polling for opportunities, qualifying matched events are pushed to your endpoint as they appear, filtered to criteria you configure.
Do I need the matched feed to use Alerts?
Yes. Alerts is an add-on gated behind an active feed key, and it fires only on the feed types your key is licensed for.
What's in an alert payload?
The same processed fields as a matched-feed row — the paired prices, rating and qualifying loss — so your handler can render or forward the event without a second API call.
Can different clients get different alerts?
Yes. Filtering is per-client: subscribe by rating band, market, bookmaker or feed type, so each client receives a stream tuned to its own users.
Related products
Notify users the moment it qualifies
Start with a matched-feed trial key, then add Relay Alerts to push opportunities to your endpoint.