canonical: https://jentic.com/apis/whapi.com/bets-api

# Whapi Bets API

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.

## For AI agents

Programmatically places a multiple or a complex bet., places a single bet. Covers 6 operations.

## Scope

Does not handle payments, communications, or crm - use for maps and geolocation only.

## Capabilities

- 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

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'places a multiple or a complex bet.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

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

## Key resources

- **Bet** — Operations for bet
- **Betslips** — Operations for betslips
- **Cashin** — Operations for cashin
- **Freebets** — Operations for freebets
- **History** — Operations for history

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Here** — Alternative maps geolocation API
- **Tomtom** — Alternative maps geolocation API
- **Googleapis** — Complementary maps geolocation API

## FAQ

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

### Can I limit what my agent is allowed to do with the Bets API?

Yes. Because you run Jentic One yourself, your own rules decide which Bets API operations the agent may call, so you can allow it to read bet history or list free bets while withholding POST /bet/single and POST /bet/complex. Since the bet id sits in the URL path, such as PUT /{betId}/cashin, you can pin a rule to cashing in one specific bet. Placing single or complex bets is never available to the agent unless you explicitly add those operations.