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.

Open source AsyncAPI → All OddsJam channels OddsJam provider profile
Provider: OddsJam AsyncAPI: v2.6.0 Spec: OddsJam (OpticOdds) Streaming API Operations: 1 Messages: 3

Channel address

/api/v3/stream/results/{sport}

Parameters

Operations

streamResults
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.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.