BetsAPI - Bet365 API
Agent-ready OpenAPI document · curated by JenticData EnrichmentData TransformationapiKey7 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Pull live, upcoming, pre-match, and finished Bet365 sports event data from BetsAPI. Read-only over seven endpoints covering in-play, upcoming, prematch odds, results, and leagues.
Use for: List all in-play football matches on Bet365 right now, Get the pre-match odds for an upcoming tennis match, Find finished results from yesterday for the Premier League, Filter live events to just basketball
Not supported: Does not handle bet placement, account funding, or non-Bet365 sportsbooks - use for read-only Bet365 in-play, upcoming, pre-match odds, league, and result data only.
Jentic publishes the only available OpenAPI specification for BetsAPI - Bet365 API, keeping it validated and agent-ready. BetsAPI provides RESTful access to Bet365 sports betting data including in-play events, upcoming fixtures, pre-match odds, league information, and finished results, giving a normalised view of Bet365 markets without scraping. It is a paid service, and the vendor's docs state that access requires purchasing the Bet365 API package. The spec covers seven read-only endpoints authenticated by a query-string token; the vendor documents six of them under /v1/bet365/ and pre-match odds under /v4/bet365/prematch.
Install Jentic One Beta
Connect the BetsAPI - Bet365 API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BetsAPI - Bet365 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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbetsapi.com%2Fbetsapi" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbetsapi.com%2Fbetsapi" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 BetsAPI - Bet365 API.
List all Bet365 in-play events currently running
Filter in-play events by sport or league
Retrieve full event detail with current odds, plus optional stats and lineup data
List upcoming Bet365 events scheduled within a time window
Pull pre-match odds for a specified event
Browse leagues and tournaments tracked by BetsAPI
Look up finished results with scores and key statistics
Use Cases
Patterns agents use BetsAPI - Bet365 API for, with concrete tasks.
★ In-Play Trading Dashboard
Power a trading dashboard that lists every live Bet365 event with current scores and key markets. /bet365/inplay returns the full live snapshot and /bet365/inplay_filter narrows it down to a sport or league of interest. /bet365/event then returns the odds and stats for any selected event, addressed by its FI event id.
Poll /bet365/inplay within the plan's hourly request budget and for each event id call /bet365/event to fetch odds and stats and update a UI
Pre-Match Odds Aggregation
Aggregate pre-match Bet365 odds against other sources to identify pricing edges. /bet365/upcoming lists scheduled events for a sport_id with a page pager, and /bet365/prematch returns price snapshots for a target FI event id. A modelling pipeline can store each snapshot and compute implied probabilities for every market. Note the vendor serves pre-match odds under /v4/bet365/prematch while the other six operations sit under /v1/.
Page through /bet365/upcoming for a sport_id and day, then GET /bet365/prematch for each FI event id and persist the price snapshot for modelling
Finished Results Backfill
Backfill historical match results into a database to train forecasting models or settle internal markets. /bet365/result returns finished events with scores and key stats addressable by event id. Combined with /bet365/upcoming for forward planning, this gives a closed loop from scheduled fixture to settled outcome suitable for time-series analysis.
Given a list of event ids that have ended, call /bet365/result for each and write the settled scores into a results table
AI Agent for Sports Insights
An AI agent uses Jentic to discover BetsAPI operations and answer sports questions: live scores, today's upcoming matches, or settled results for a team. The agent searches by intent, loads the operation schema from Jentic, and executes against BetsAPI without learning the Bet365 endpoint surface or its per-operation version prefixes manually.
Search Jentic for 'list in-play bet365 events' and execute the returned /bet365/inplay operation filtered to football, then summarise live scores
Key Endpoints
7 endpoints — jentic publishes the only available openapi specification for betsapi - bet365 api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/bet365/inplay
List all in-play events
GET
/bet365/inplay_filter
Filter in-play events by sport and league
GET
/bet365/event
Get detail for a specific event id
GET
/bet365/upcoming
List upcoming events
GET
/bet365/prematch
Pre-match odds for an event
GET
/bet365/league
List leagues
GET
/bet365/result
Finished event results
GET
/bet365/inplay
List all in-play events
GET
/bet365/inplay_filter
Filter in-play events by sport and league
GET
/bet365/event
Get detail for a specific event id
GET
/bet365/upcoming
List upcoming events
GET
/bet365/prematch
Pre-match odds for an event
GET
/bet365/league
List leagues
GET
/bet365/result
Finished event results
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the BetsAPI Bet365 API by hand means appending your token as a query parameter, learning the inplay, upcoming, prematch, and result endpoints, and parsing the odds responses yourself. Through Jentic you install once, import the BetsAPI Bet365 API from the API Directory, store the token once, and your agent calls it.
Permission scoping
BetsAPI is read-only and carries its filters as query parameters rather than as a resource in the URL path, so scope the agent to the operations it needs, such as reading in-play or pre-match events. You choose that operation set, and there are no write operations to add.
Credential isolation
Your BetsAPI token is stored once, encrypted, by your own Jentic One instance and appended as the token query parameter at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'live Bet365 events' or 'pre-match odds', and Jentic returns the matching BetsAPI operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using BetsAPI - Bet365 API through Jentic.
Why is there no official OpenAPI spec for BetsAPI - Bet365 API?
BetsAPI does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call BetsAPI - Bet365 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 BetsAPI Bet365 API use?
BetsAPI uses an API token passed as the token query parameter, which the docs instruct you to pass as token= in the GET query. Tokens come from BetsAPI support or the Orders page in your BetsAPI account, and they carry whichever package you bought: the Bet365 API package is the one that covers these operations. When called via Jentic, the token is stored encrypted by your own Jentic One instance and appended at execution time so it never appears in the agent's context.
Can I filter in-play events to a specific sport?
Yes. GET /bet365/inplay_filter accepts a sport identifier and optional league filter, returning only matching live events. This is preferable to filtering /bet365/inplay client-side when you only care about a subset of sports because it reduces payload size.
How do I retrieve pre-match odds through Jentic?
Search Jentic for 'bet365 prematch odds'. Jentic returns GET /bet365/prematch, the agent loads its parameter schema, and executes it with the FI event id obtained from GET /bet365/upcoming. The response includes price snapshots per market. Note that the vendor serves this one operation under /v4/bet365/prematch while the other six Bet365 operations sit under /v1/.
What rate limits apply to the BetsAPI Bet365 API?
The BetsAPI docs state that all APIs are limited by default to 3600 requests per hour, reported back in the X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset response headers, and that Volume Packages can be bought to raise the hourly ceiling. The OpenAPI spec does not encode this, so cache responses where possible and honour 429 responses with backoff before scaling polling frequency.
Is the BetsAPI Bet365 API free?
No. The BetsAPI docs describe it as a paid service starting at $10 per month, and state that you must purchase the relevant package before you can access an API. Packages are split by bookmaker family, and the Bet365 API package is the one that covers these operations. The vendor sells cheap trial packages rather than a free tier, and caps how many times each trial can be bought.
Is there a BetsAPI MCP server?
You do not need an MCP server to give your agent the BetsAPI Bet365 API. Jentic connects it directly from the API Directory: import the API, keep your BetsAPI token in your self-hosted instance, and the agent calls the Bet365 operations on demand without another server's tool definitions sitting in its context.
Can I limit what my agent is allowed to do with the BetsAPI Bet365 API?
Yes. Because you run Jentic One self-hosted, your own rules decide which BetsAPI operations and credentials the agent may use, and you can grant only the endpoints it needs, such as GET /bet365/inplay for live events or GET /bet365/prematch for pre-match odds while withholding /bet365/result or /bet365/league. BetsAPI is entirely read-only and passes its filters as query parameters rather than path resources, so there are no write operations to expose. Your BetsAPI token is stored encrypted by your own instance and appended at execution time, never entering the agent's prompt or context.
GET STARTED