Can HumDay connect to Whapi Sessions?

Yes. HumDay reads Whapi Sessions's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 4 operations are documented.

Do I need to write code to automate Whapi Sessions?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Whapi Sessions account.

What can HumDay do in Whapi Sessions?

2 of the 4 documented operations change something in Whapi Sessions, and 2 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Whapi Sessions account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Whapi Sessions is held behind that approval.

Automate Whapi Sessions

HumDay reads Whapi Sessions’s own published API description and derives 4 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Whapi Sessions is

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. To authenticate, you’ll need to supply a sportsbook username and password, in return you will be given an authentication ticket, which you can use on the majority of requests found within our services. The Sessions API

API host: sandbox.whapi.com

What HumDay can do in Whapi Sessions

2 documented operations change something in Whapi Sessions.

POSTLogs in a customer and obtains an authentication ticket./tickets
DELETELog out a customer./tickets/{tgt}

What HumDay can read from Whapi Sessions

These are the operations a schedule or a trigger can watch.

GETChecks the validity of a session ticket./tickets/{tgt}
GETObtains a one-time Service Ticket that can be used to access other William Hill services./tickets/{tgt}/serviceTicket

How automating Whapi Sessions works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Whapi Sessions account.
Grant access, then go live. You approve the specific Whapi Sessions operations it may use — and only those.