AsyncAPI channel · OddsJam · OddsJam (OpticOdds) Streaming API

copilot-queue

RabbitMQ queue delivering copilot odds updates. The queue name is returned by the REST control endpoint `POST /api/v3/copilot/queue/start`. Lifecycle is also managed by `POST /api/v3/copilot/queue/stop` and `GET /api/v3/copilot/queue/status`. Messages are pulled (no push). The pika example uses a prefetch of 100 and auto-acknowledgement.

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

copilot-queue

Operations

consumeCopilotQueue
Consume copilot odds messages from the assigned RabbitMQ queue.

Messages

copilot-queue-message
AMQP message body delivered through the copilot queue. Exchange naming and full envelope schema are not enumerated in the public documentation; contact OpticOdds sales for implementation specifics.
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.