canonical: https://jentic.com/apis/cloudbet.com/cloudbet-feed

# Cloudbet Feed API

Jentic publishes the only available OpenAPI specification for Cloudbet Feed API, keeping it validated and agent-ready. The Cloudbet Feed API delivers real-time sports odds, fixtures, and market data across sports such as soccer, basketball, and baseball. Authentication uses a long-lived JWT-format API key passed via the X-API-Key header, with separate Trading and Affiliate keys controlling latency and bet placement rights. Responses are available as JSON or binary protobuf, allowing low-overhead ingestion into trading systems, dashboards, or model pipelines.

## For AI agents

Fetch real-time sports odds, fixtures, competitions, and market lines from Cloudbet across global sporting events using a JWT API key.

## Scope

Does not place bets, manage account balances, or process payouts - use for reading sports odds and fixtures only.

## Capabilities

- Retrieve match odds, Asian handicap, and totals markets for soccer competitions
- List all available sports and competitions with their hierarchy keys
- Fetch fixtures and event schedules filtered by sport, competition, or date
- Pull current odds lines for individual events and markets
- Stream odds updates in JSON or binary protobuf for low-latency ingestion
- Look up event metadata and trading status by event ID

## Use cases

### Sports Odds Aggregation

Ingest live and pre-match odds from Cloudbet into an aggregator or comparison product. The Feed API exposes sports, competitions, events, and lines under `/v2/odds`, with both JSON and protobuf payloads so downstream services can choose the lowest-overhead path. Trading API keys give real-time updates while Affiliate keys are cached up to one minute.

Example prompt: Call GET `/v2/odds/competitions/soccer-england-premier-league` with markets=soccer.matchOdds and return all current match odds for the next gameweek.

### Pricing Model Data Pipeline

Feed quantitative trading or risk models with structured odds data. Use `/v2/odds/sports` to enumerate the catalogue, `/v2/odds/fixtures` to pull schedules, and `/v2/odds/events/{id}` to refresh per-event lines. Binary protobuf responses reduce parse overhead in tight loops.

Example prompt: Fetch GET `/v2/odds/fixtures` for sport=basketball and load each event's lines via GET `/v2/odds/events/{id}` into the model input table.

### Fixture and Event Discovery

Build a fixture browser or chatbot that answers what games are coming up. Combine `/v2/odds/sports` and `/v2/odds/competitions/{key}` to surface a navigable catalogue, then drill into `/v2/odds/events` for schedule details. The API returns market keys you can use to scope subsequent odds queries.

Example prompt: Call GET `/v2/odds/sports`, then GET `/v2/odds/competitions/{key}` for soccer, then GET `/v2/odds/fixtures` filtered by the next 7 days.

### AI Agent Odds Lookup

Let a Jentic-powered agent answer odds questions in natural language. The agent searches Jentic for 'get sports odds', loads the Cloudbet operation schema, and executes `/v2/odds/competitions/{key}` or `/v2/odds/events/{id}` with the resolved key. Credentials stay in your Jentic One instance.

Example prompt: Search Jentic for 'fetch live sports odds', load the Cloudbet getOddsByEvent operation, and execute it for a given event ID.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v2/odds/sports` | List all sports with metadata |
| GET | `/v2/odds/sports/{key}` | Get details for a single sport |
| GET | `/v2/odds/competitions/{key}` | Get competition data including markets |
| GET | `/v2/odds/events` | List events across competitions |
| GET | `/v2/odds/events/{id}` | Get a single event with current lines |
| GET | `/v2/odds/fixtures` | List scheduled fixtures |
| GET | `/v2/odds/lines` | Get current market lines |

## Key resources

- **Sports** — Top-level sport catalogue and per-sport metadata under `/v2/odds/sports.`
- **Competitions** — League and tournament data with markets at `/v2/odds/competitions/{key}.`
- **Events** — Individual fixtures with status, participants, and lines under `/v2/odds/events.`
- **Fixtures** — Scheduled events filtered by sport and date at `/v2/odds/fixtures.`
- **Lines** — Current market lines and prices at `/v2/odds/lines.`

## Why Jentic

- **Setup:** Wiring the Cloudbet Feed API by hand means adding your X-API-Key header on every request and pointing calls at sports-api.cloudbet.com/pub yourself. Through Jentic you install once, import the Cloudbet Feed API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Feed API is read-only and identifies sports, competitions, and events through request parameters rather than a resource id fixed in the URL path, so scope the agent by the operations it needs, such as reading sports, listing fixtures, or fetching odds lines. You choose that set, so it only reaches the feed operations you include.
- **Credential handling:** Your Cloudbet X-API-Key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get live sports odds' or 'list soccer fixtures', and Jentic returns the matching Cloudbet operation with its input schema so the agent calls the right `/v2/odds` endpoint without browsing the docs.

## Related APIs

- **Cloudbet Sports Betting API** — Adds Trading and Account endpoints on top of the same odds feed.
- **The Odds API** — Aggregates odds from many bookmakers rather than a single sportsbook.
- **Cloudbet Sports Betting API** — Larger 15-endpoint surface combining Feed, Trading, Account and Affiliate.

## FAQ

### Why is there no official OpenAPI spec for Cloudbet Feed API?

Cloudbet does not publish a structured OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cloudbet Feed API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Cloudbet Feed API use?

The Feed API uses an API key in the X-API-Key header. The key follows the JWT standard and comes in two variants: a Trading key for real-time data and an Affiliate key whose responses may be cached up to one minute. Through Jentic, the key is stored encrypted in the vault and never enters the agent context.

### Can I retrieve live in-play odds with the Cloudbet Feed API?

Yes. Events transition through statuses such as TRADING and TRADING_LIVE, and GET `/v2/odds/events/{id}` returns the current lines for live events. Use a Trading API key for real-time updates rather than the cached Affiliate path.

### What sports are covered by the Cloudbet Feed API?

Call GET `/v2/odds/sports` to enumerate the full catalogue, which includes soccer, baseball, basketball, tennis, esports and more. Each sport exposes competitions and market keys you can pass to GET `/v2/odds/competitions/{key}.`

### How do I fetch Premier League odds through Jentic?

Run jentic search 'get soccer match odds for a competition', load the Cloudbet getOddsByCompetition operation, and execute it with key=soccer-england-premier-league and markets=soccer.matchOdds. Jentic handles the X-API-Key header from the stored credential.

### Does the Cloudbet Feed API support binary protobuf responses?

Yes. Set Content-Type: application/x-protobuf to receive binary protobuf payloads instead of JSON. This reduces parse overhead for high-throughput ingestion into pricing or risk models.

### Can I limit what my agent is allowed to do with the Cloudbet Feed API?

Yes. Because Jentic One is self-hosted, you decide which Cloudbet Feed operations your agent may call, and it can only reach the ones you include. The Feed API is read-only and selects sports, competitions, and events through request parameters rather than a fixed resource id in the URL, so you scope the agent to just the operations it needs, such as listing sports, fetching fixtures, or reading odds lines. Your rules govern which operations and credentials the agent uses, so it cannot touch anything beyond the set you grant.