Whapi Bets API
Browse all Whapi APIs★ Only Publicly Available OpenAPI DocumentMaps GeolocationPlaces Searchnone6 EndpointsREST
For Agents
Programmatically places a multiple or a complex bet., places a single bet. Covers 6 operations.
Use for: I need to places a multiple or a complex bet., I want to places a single bet, Search for validatebetslip, Find all returns available free bets
Not supported: Does not handle payments, communications, or crm - use for maps and geolocation only.
The Bets API methods are used to place single, multiple and complex bets and to retrieve a customer’s bet history. When retrieving a customer’s bet history you can organize the bets from the betting history in terms of date, bet type and whether the bet is settled or not. You can also specify what fields to be included/excluded or return a list of all default fields the method returns. <br /><br /. The API exposes 6 endpoints.
Install Jentic One Beta
Connect the Bets API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bets 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%2Fwhapi.com%2Fbets-api" | 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%2Fwhapi.com%2Fbets-api" | 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 Bets API.
Places a multiple or a complex bet.
validateBetslip
Returns available free bets
Retrieves the customer’s bet history.
Allows a trusted application to cash in a bet (take a return on a bet) on behalf
Use Cases
Patterns agents use Bets API for, with concrete tasks.
★ Maps and Geolocation Operations
Use the Bets API to perform maps geolocation operations programmatically. The API provides 6 endpoints covering core functionality including places a multiple or a complex bet., places a single bet, validatebetslip.
Call POST /bet/complex to places a multiple or a complex bet.
Automated Bet Management
Automate bet operations by combining multiple Bets API endpoints. Agents can places a single bet and then validatebetslip in a single workflow.
Call POST /bet/single to places a single bet, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Bets API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'places a multiple or a complex bet.', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
6 endpoints — the bets api methods are used to place single, multiple and complex bets and to retrieve a customer’s bet history.
METHOD
PATH
DESCRIPTION
POST
/bet/complex
Places a multiple or a complex bet.
POST
/bet/single
Places a single bet
POST
/betslips
validateBetslip
GET
/freebets
Returns available free bets
GET
/history
Retrieves the customer’s bet history.
PUT
/{betId}/cashin
Allows a trusted application to cash in a bet (take a return on a bet) on behalf
POST
/bet/complex
Places a multiple or a complex bet.
POST
/bet/single
Places a single bet
POST
/betslips
validateBetslip
GET
/freebets
Returns available free bets
GET
/history
Retrieves the customer’s bet history.
PUT
/{betId}/cashin
Allows a trusted application to cash in a bet (take a return on a bet) on behalf
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring this Bets API by hand means pointing requests at its sandbox.whapi.com host, wiring each bet operation, and handling retries yourself. Through Jentic you install once, import the Bets API from the API Directory, and your agent calls it.
Permission scoping
This Bets API puts the bet id in the URL path (/{betId}/cashin), so a rule can pin an operation to acting on one bet. You choose the operations it may call, so placing single or complex bets is not included unless you add them.
Credential isolation
This Bets API declares no authentication in its spec, so there is no credential to store; if your instance later adds one, Jentic One stores it once, encrypted, and injects it at execution time so it never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'read available free bets' or 'cash in a bet', and Jentic returns the matching Bets API operation with its input 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 Bets API through Jentic.
What authentication does the Bets API use?
The Bets API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I places a multiple or a complex bet. with the Bets API?
Yes. Use the POST /bet/complex endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Bets API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I places a multiple or a complex bet. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'places a multiple or a complex bet.'. Jentic returns the matching Bets API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Bets API have?
The Bets API exposes 6 endpoints covering bet, betslips, cashin operations.
GET STARTED