canonical: https://jentic.com/apis/cloudbet.com/cloudbet-sports-betting # Cloudbet Sports Betting API The Cloudbet Sports Betting API combines the public Feed (sports, competitions, events, fixtures, lines), the Trading endpoints for placing single and multiple bets, and the Account balance and Affiliate analytics operations into one surface. Authentication is a JWT-format API key passed in the X-API-Key header, with separate Trading and Affiliate key types that Cloudbet documents for placing bets and for consuming odds respectively. It covers 15 endpoints across odds discovery and bet placement. ## For AI agents Read sports odds, place straight or multiple bets, and check bet status on Cloudbet using a JWT API key. ## Scope Covers sports odds, bet placement, account balances, and affiliate analytics only; the spec declares no casino, payment, or KYC operations. ## Capabilities - Place single straight bets via `/v4/bets/place/straight` - Place multi-leg accumulator bets via `/v4/bets/place/multiple` - Look up the status and settlement of submitted bets - Retrieve sports, competitions, events, fixtures, and current lines for pricing - Pull account balances and currency information for the authenticated player - Pull aggregated or grouped affiliate analytics via `/v1/affiliate/analytics`, up to a 31-day range ## Use cases ### Programmatic Bet Placement Submit bets from a trading bot or model. Use `/v2/odds` endpoints to read live prices, then POST to `/v4/bets/place/straight` or `/v4/bets/place/multiple` with the chosen selection and stake. Bet status can be polled through the bets endpoints to confirm settlement. Example prompt: Call POST `/v4/bets/place/straight` with a referenceId, currency, stake, priceChange, and a selection carrying eventId, marketUrl, and price, then poll GET `/v4/bets` to confirm acceptance. ### Live Odds Trading Dashboard Power a real-time trading screen that shows market odds and lets a user place wagers in one place. Pull from `/v2/odds/events` and `/v2/odds/lines` for prices, `/v4/bets/place/multiple` for combo bets, and the Account endpoints to display balance. A Trading API key gives real-time updates, which Cloudbet contrasts with the Affiliate key's cached Feed responses. Example prompt: Poll GET `/v2/odds/events` with sport=basketball and live=true, render the lines, and call POST `/v4/bets/place/straight` when a user clicks a price. ### Affiliate Odds Distribution Republish Cloudbet odds on an affiliate site. The Affiliate API key gives access to the same `/v2/odds` endpoints with cached responses up to one minute old, suitable for comparison pages or content sites. Cloudbet documents the Affiliate key for consuming odds without placing bets programmatically, and the Trading key as the one meant for bet placement. Example prompt: Authenticate with an Affiliate key, read the competition keys from GET `/v2/odds/sports/{key}` for soccer, then call GET `/v2/odds/competitions/{key}` to render today's match odds widget. ### AI Agent Betting Workflow Let a Jentic-powered agent execute a full bet workflow: search for odds, evaluate against a strategy, and place a stake. The agent uses Jentic to discover the right Cloudbet operation by intent, loads its schema, and executes - Cloudbet credentials never leave your Jentic One instance. Example prompt: Search Jentic for 'place a sports bet on Cloudbet', load the placeStraightBet operation, and execute with the chosen event, market, and stake. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/v2/odds/sports` | List all sports | | GET | `/v2/odds/competitions/{key}` | Get a competition with markets | | GET | `/v2/odds/events/{id}` | Get a single event with lines | | POST | `/v2/odds/lines` | Get the current line for a market selection | | POST | `/v4/bets/place/straight` | Place a single straight bet | | POST | `/v4/bets/place/multiple` | Place a multi-leg accumulator | | GET | `/v4/bets` | List submitted bets and status | ## Key resources - **Feed** — Sports, competitions, events, fixtures, and lines under `/v2/odds.` - **Trading** — Bet placement and lookup under `/v4/bets.` - **Account** — Player account, balances, and currency endpoints. - **Affiliate** — Aggregated and grouped referral analytics under `/v1/affiliate.` ## Why Jentic - **Setup:** Wiring the Cloudbet Sports Betting API by hand means adding your X-API-Key header on every request and pointing both the `/v2/odds` reads and the `/v4/bets` writes at sports-api.cloudbet.com/pub yourself. Through Jentic you install once, import the Cloudbet Sports Betting API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Cloudbet passes the bet details in the request body rather than fixing a resource id in the URL path, so scope the agent by the operations it needs, such as reading odds lines or listing current bets. You choose that set, so bet-placing operations like straight or multiple placement are only in reach if you include them. - **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 'place a sports bet' or 'list current bets', and Jentic returns the matching Cloudbet `/v4/bets` or `/v2/odds` operation with its input schema so the agent calls the right endpoint without browsing the docs. ## Related APIs - **Cloudbet Feed API** — The same vendor's 7-endpoint odds feed, without the Trading endpoints. - **The Odds API** — Aggregates odds across many bookmakers but does not support bet placement. ## FAQ ### Which OpenAPI specification does this page describe for the Cloudbet Sports Betting API? Cloudbet publishes its own OpenAPI documents, listed at `https://www.cloudbet.com/api/`, but splits them by product: a Feed API document with the 7 odds operations, a Trading API document with the 3 bet operations, and an Account API document with the 5 account and affiliate operations. This page describes a curated, agent-optimized Jentic variant that consolidates the same 15 operations into a single file and lifts the /pub prefix out of the Trading paths into the server URL, so an agent can discover the whole surface at once. Read Cloudbet's own documents when you only need one product area. ### What authentication does the Cloudbet Sports Betting API use? The API uses an X-API-Key header carrying a JWT-format API key. Cloudbet issues two key types and documents the Trading key as the one meant for developers who want to place bets programmatically, and the Affiliate key as primarily meant for consuming odds without needing to place bets. Through Jentic, the key is stored encrypted and injected at execution time only. ### Can I place accumulator bets with the Cloudbet Sports Betting API? Yes. POST `/v4/bets/place/multiple` takes a selections array in one request under a single client-supplied referenceId, so one bet covers the whole accumulator. Each leg carries eventId, marketUrl, and price taken from the `/v2/odds` feed. ### How do I check the status of a placed bet? Call GET `/v4/bets`, which returns each bet's referenceId, status, result, and payout, and narrow the list with the status query parameter. Polling is appropriate because settlement depends on the underlying event finishing. ### Is the Cloudbet Sports Betting API rate limited? Yes, on bet placement. The spec states that POST `/v4/bets/place/straight` and POST `/v4/bets/place/multiple` are each rate limited to 2 requests per second, and both return 429 with X-RateLimit-Limit and X-RateLimit-Remaining headers when that ceiling is exceeded. Read the remaining allowance from those headers and back off instead of retrying immediately. The spec documents the limit only on those two operations. ### How do I place a bet through Jentic? Ask your agent for what you want, such as 'place a sports bet on Cloudbet'. Jentic returns the matching placeStraightBet operation with its input schema, and the agent executes it with the eventId, marketUrl, price, currency, and stake. Jentic injects the X-API-Key from the stored Trading credential. ### Are there separate keys for reading odds and placing bets? Yes. Cloudbet documents the Trading key for developers who want to place bets programmatically and give real-time updates, and the Affiliate key for consuming odds without placing bets, where Feed responses may be cached and up to 1 minute behind. Pick the key type that matches the intended workload. ### Is there a Cloudbet Sports Betting API MCP server? You do not need an MCP server to give your agent the Cloudbet Sports Betting API. Jentic connects it directly from the API Directory: import the API, store your X-API-Key once in your own Jentic One instance, and your agent reaches all 15 operations, discovered on demand rather than loaded into its context up front. ### Can I limit what my agent is allowed to do with the Cloudbet Sports Betting API? Yes. Because you run Jentic One yourself, your own rules decide which Cloudbet operations and credentials the agent can use, and Cloudbet passes bet details in the request body rather than fixing a resource in the URL, so you scope the agent by the operation set you grant. You can allow only read operations like GET `/v2/odds/events` and GET `/v4/bets` while withholding the write operations, so bet placement through POST `/v4/bets/place/straight` and POST `/v4/bets/place/multiple` is out of reach unless you include it. You also control which key is stored, so storing an Affiliate key, which Cloudbet documents for consuming odds rather than placing bets programmatically, keeps the stored credential aligned with an odds-reading workload.