AsyncAPI channel · OddsJam · OddsJam (OpticOdds) Streaming API

fixtures-results-queue

RabbitMQ queue delivering fixture results updates. Queue name is issued by `POST /api/v3/fixtures/results/queue/start`; lifecycle is managed via `POST /api/v3/fixtures/results/queue/stop` and `GET /api/v3/fixtures/results/queue/status`.

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

Channel address

fixtures-results-queue

Operations

consumeFixturesResultsQueue
Consume fixture results messages from the assigned RabbitMQ queue.

Messages

fixture-results-queue-message
AMQP message body delivered through the fixtures results queue. Envelope schema is not enumerated in the public documentation.
Content-Type: application/json

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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.