Whapi Bets API

Name: Bets API
Brand: Bets API
Availability: InStock

★ 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

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.

Step 1: 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

Step 2: 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 Bets API.

Places a multiple or a complex bet.

validateBetslip

Returns available free bets

Retrieves the customer’s bet history.

GET STARTED

Start building with Bets API

Explore with Jentic

View OpenAPI Document

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

Why Jentic?

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

Credential isolation

Bets API none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'places a multiple or a complex bet.') and Jentic returns the matching Bets API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Bets API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

Whapi Bets API

Connect the Bets API to your agent

Capabilities

Start building with Bets API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs