Cloudbet Sports Betting API

Name: Cloudbet Sports Betting API API
Brand: Cloudbet Sports Betting API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey15 EndpointsREST

For Agents

Read sports odds, place straight or multiple bets, and check bet status on Cloudbet using a JWT API key.

Connect the Cloudbet Sports Betting API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloudbet Sports Betting API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Cloudbet Sports Betting API API.

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

GET STARTED

Start building with Cloudbet Sports Betting API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Cloudbet Sports Betting API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Cloudbet Sports Betting API, keeping it validated and agent-ready. The Cloudbet Sports Betting API combines the public Feed (sports, competitions, events, fixtures, lines), the Trading endpoints for placing single and multiple bets, and Account and Affiliate operations into one surface. Authentication is a JWT-format API key passed in the X-API-Key header, with separate Trading and Affiliate keys controlling latency and bet permissions. It covers 15 endpoints across odds discovery and bet placement.

Use Cases

Patterns agents use Cloudbet Sports Betting API API for, with concrete tasks.

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

Call POST /v4/bets/place/straight with eventId, marketUrl, side, price, and stake=20 USD, 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 keeps prices live with no caching.

Subscribe to GET /v2/odds/events for sport=basketball, render lines, and call POST /v4/bets/place/straight when a user clicks a price.

Affiliate Odds Distribution

Republish Cloudbet odds on an affiliate site without bet placement rights. 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. Trading endpoints reject Affiliate keys.

Authenticate with an Affiliate key and call GET /v2/odds/competitions/{key} for soccer-italy-serie-a 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 the Jentic vault.

Search Jentic for 'place a sports bet on Cloudbet', load the placeBet operation, and execute with the chosen event, market, and stake.

Key Endpoints

15 endpoints — jentic publishes the only available openapi specification for cloudbet sports betting api, keeping it validated and agent-ready.

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

GET

/v2/odds/lines

Get current market lines

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

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

GET

/v2/odds/lines

Get current market lines

POST

/v4/bets/place/straight

Place a single straight bet

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Cloudbet Trading or Affiliate X-API-Key is stored encrypted in the Jentic vault. Agents receive scoped access tokens — the raw JWT never enters the agent's context, which is critical when bet placement rights are involved.

Intent-based discovery

Agents search Jentic by intent (for example 'place a sports bet' or 'list current bets') and Jentic returns the matching Cloudbet /v4/bets or /v2/odds operation with its input schema.

Time to first call

Direct Cloudbet integration: 3-5 days covering JWT key setup, odds ingest, bet submission, and reconciliation. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Cloudbet Feed API

Read-only odds feed without the Trading endpoints.

Pick the Feed API when the agent only needs odds and fixtures and should not be able to place bets.

Alternative

The Odds API

Aggregates odds across many bookmakers but does not support bet placement.

Use The Odds API when the agent needs cross-bookmaker pricing for arbitrage or comparison rather than executing bets on a single sportsbook.

Alternative

Cloudbet Feed API

Smaller 7-endpoint odds-only surface from the same vendor.

Choose the Feed API for lighter integrations that only need odds reads.

FAQs

Specific to using Cloudbet Sports Betting API API through Jentic.

Why is there no official OpenAPI spec for Cloudbet Sports Betting API?

Cloudbet does not publish a structured OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cloudbet Sports Betting API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Cloudbet Sports Betting API use?

The API uses an X-API-Key header carrying a JWT-format API key. A Trading key is required to call the /v4/bets endpoints, while Affiliate keys are limited to cached /v2/odds reads. 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 accepts multiple selections in one request and returns a single bet ID covering the accumulator. Each leg references an event, market, side, and price taken from the /v2/odds feed.

How do I check the status of a placed bet?

Call GET /v4/bets to list submitted bets with their current status, or query for an individual bet to see settlement and payout details. Polling is appropriate because settlement depends on the underlying event finishing.

How do I place a bet through Jentic?

Run jentic search 'place a sports bet on Cloudbet', load the placeBet operation schema, then execute with the event ID, market URL, side, price, and stake. Jentic handles the X-API-Key from the stored Trading credential.

Are there separate keys for reading odds and placing bets?

Yes. The Trading API key allows real-time odds reads and bet placement, while the Affiliate key only allows cached odds reads. Pick the key type that matches the intended workload — POSTs to /v4/bets reject Affiliate keys.