BetsAPI - Bet365 API

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.