AsyncAPI channel · OddsJam
· OddsJam (OpticOdds) Streaming API
/api/v3/stream/results/{sport}
Server-Sent Events stream of live scores, game outcomes, and player performance data. OpticOdds recommends a separate connection per league rather than passing multiple leagues per request.
Receive fixture-results, ping, and connected events.
Messages
connected
Confirms successful SSE stream initialization.
Content-Type: text/event-stream
ping
Periodic keepalive (approximately every 5 seconds) carrying a server timestamp for drift detection.
Content-Type: text/event-stream
fixture-results
Delivers updated match data matching the `/fixtures/results` and `/player-results` REST schemas.
Content-Type: text/event-stream
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.