Log out a customer in Whapi Sessions

What this operation does

Log out a customer.

• DELETEChanges data · Sessionssandbox.whapi.com/tickets/{tgt}

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Whapi Sessions operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Whapi Sessions operations

• Logs in a customer and obtains an authentication ticketPOST · changes data
• Checks the validity of a session ticketGET · reads data
• Obtains a one-time Service Ticket that can be usedGET · reads data

All 4 Whapi Sessions operations

Questions

Can HumDay log out a customer in Whapi Sessions?

Yes. This operation is published in Whapi Sessions's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my Whapi Sessions data?

Yes — this is a DELETE operation, so it changes something in Whapi Sessions. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

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

Where this came from

Read from a published API description for Whapi Sessions at developer.williamhill.com/wh-docs/docs-sdks/sessions/swagger/docs. The description above is the provider’s own wording, not ours. Last published 2021-06-21.