Public APIs / Entertainment / Whapi APIs
Whapi APIs
6 REST APIs from whapi.com, each with an OpenAPI spec. The Bets API methods are used to place single, multiple and complex bets and to retrieve a customer’s bet history.
Open the Whapi APIs documentation Build something with it
Key facts
- Category
- Entertainment
- Authentication
- See docs
- HTTPS
- Unknown
- CORS
- Unknown
- Listed in
- APIs.guru
Authentication is described in the provider's OpenAPI spec and documentation. Most need a key or OAuth.
What you could build with Whapi APIs
Entertainment APIs return jokes, quotes, trivia and pop-culture data.
- A quiz or trivia game
- Daily content for a newsletter or social page
- An event night app for bars and venues
OpenAPI spec
Whapi APIs has a machine-readable OpenAPI definition. Load it into Postman, Insomnia or a code generator to get every endpoint and a typed client in minutes.
6 Whapi APIs REST APIs
- Bets API 2.0.0
The Bets API methods are used to place single, multiple and complex bets and to retrieve a customer’s bet history spec - Locations 2.0
The Locations API is a collection of methods that support geographical information. The first method is an address lookup service for UK addresses spec - Numbers API 2.0
The William Hill Numbers API uses a single method that allows you to generate random numbers for your application spec - Accounts API 2.0.0
The Accounts API is a collection of methods used to query a customer account. It allows the developer to retrieve account-related data such as the user account balance spec - Sessions API 2.0.0
The William Hill Sessions API uses a central authentication service (CAS*) on all resources that require access to a customer’s account or betting functionality spec - SportsData API 2
The William Hill SportsData REST API is a collection of GET methods to provide William Hill product data such as sport, competition, event, market and selection data (including prices) spec
How we would integrate Whapi APIs
- Generate a typed client from the OpenAPI spec, so every endpoint and field is checked at build time.
- Sign up with the provider, get a key and store it on the server in an env.php or secret store.
- Put a small backend in front of it, so the browser talks to your server and your server talks to the API.
- Cache results in your own database, so pages stay fast and you stay inside rate limits.
- Add monitoring: if the API goes down or changes, you get an alert before your customers notice.
Questions about Whapi APIs
Does the Whapi APIs need an API key?
Authentication is described in the provider's OpenAPI spec and documentation. Most need a key or OAuth.
Is there an OpenAPI (Swagger) spec for Whapi APIs?
Yes. The spec is linked on this page, so you can generate a client or import it into Postman.
Can I call Whapi APIs from the browser?
It is not documented. Plan for a small server-side proxy to be safe.
Does Whapi APIs support HTTPS?
Not according to the list. Call it from a server, not from a secure web page.
Can you build an app with Whapi APIs for me?
Yes. FullStack Partner has developers who build and run products on APIs like this one. Send us a few lines and we reply with a plan and a fixed price.