William Hill APIs for AI Agents
E CommerceStorefrontForms SurveysThird-Party SpecsNo authAPI keyAgent Ready
www.williamhill.com·Developer portal → developer.williamhill.com
William Hill API Catalog
6 APIs across 6 product groups.
Developer Tools1
Maps Geolocation1
Which William Hill API should I use?
| I want to... | Use | Why |
|---|---|---|
| Read sports competitions, events, markets and prices | SportsData API | SportsData API returns competition, event, market and selection data including prices for building a betslip |
| Authenticate a customer and get a session ticket | Sessions API | Sessions API logs in a customer and issues, validates and revokes the authentication ticket other calls rely on |
| Place bets and read bet history | Bets API | Bets API places single, multiple and complex bets, validates betslips, and returns settled and unsettled history |
| Read a customer's balance, payments and card details | Accounts API | Accounts API queries account details, balance, payments and Plus Card status for the logged-in customer |
| Resolve a UK address, country or currency | Locations | Locations returns address lookups and reference data for countries and currencies to populate registration forms |
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Instead of wiring each William Hill API against its whapi.com sandbox host and stitching the session, sports data, betting and account calls together by hand, you install Jentic One once and add the APIs you need from the Jentic directory, then your agent calls them.
Permission scoping
Your own Jentic One rules decide which operations each API exposes to the agent. You can allow read-only sports data and balance lookups while withholding write actions such as placing bets or reporting a Plus Card lost until you add them explicitly.
Credential isolation
Where an API needs a key, such as the Locations apiKey, your own Jentic One instance stores it once, encrypted, and injects it at execution time so it never enters the agent's prompt, logs, or context. Session tickets from the Sessions API are handled the same way.
FAQs
Specific to using William Hill APIs through Jentic.
What can an agent build across the William Hill APIs?
An agent can run a full sportsbook flow: authenticate a customer with the Sessions API, read competitions, events, markets and prices from the SportsData API, place and track bets with the Bets API, and query balances, payments and card details with the Accounts API. The Locations and Numbers APIs supply supporting address, reference and random-number data.
Do these APIs share one set of credentials?
No. The Locations API uses an apiKey header, while the other five rely on a session ticket issued by the Sessions API for any call that touches a customer's account or betting. You authenticate once through the Sessions API and reuse the ticket across the account, betting and sports data calls that require it.
Which API should an agent start with?
For anything customer-specific, start with the Sessions API to obtain an authentication ticket. For read-only market data an agent can call the SportsData API directly, then move to the Bets and Accounts APIs once a session exists.
Are these production or sandbox endpoints?
The specs point at the whapi.com sandbox host. Treat them as test endpoints for building and validating flows, and confirm production hosts and credentials with William Hill before handling real customer accounts or stakes.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
