Whapi Sessions API

Name: Sessions API
Brand: Sessions API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthenticationnone4 EndpointsREST

Install Jentic One Beta

Connect the Sessions API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sessions 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 Sessions API.

Logs in a customer and obtains an authentication ticket.

Checks the validity of a session ticket.

Log out a customer.

Obtains a one-time Service Ticket that can be used to access other William Hill

GET STARTED

Start building with Sessions API

Explore with Jentic

View OpenAPI Document

For Agents

Programmatically logs in a customer and obtains an authentication ticket., checks the validity of a session ticket.. Covers 4 operations.

Use for: I need to logs in a customer and obtains an authentication ticket., I want to checks the validity of a session ticket., Search for log out a customer., Find all obtains a one-time service ticket that can be used to access other william hill

Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.

Use Cases

Patterns agents use Sessions API for, with concrete tasks.

★ Identity and Authentication Operations

Use the Sessions API to perform identity auth operations programmatically. The API provides 4 endpoints covering core functionality including logs in a customer and obtains an authentication ticket., checks the validity of a session ticket., log out a customer..

Call POST /tickets to logs in a customer and obtains an authentication ticket.

Automated Tickets Management

Automate tickets operations by combining multiple Sessions API endpoints. Agents can checks the validity of a session ticket. and then log out a customer. in a single workflow.

Call GET /tickets/{tgt} to checks the validity of a session ticket., then verify the result

AI Agent Integration via Jentic

AI agents discover and call Sessions 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 'logs in a customer and obtains an authentication ticket.', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

4 endpoints — 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.

METHOD

PATH

DESCRIPTION

POST

/tickets

Logs in a customer and obtains an authentication ticket.

GET

/tickets/{tgt}

Checks the validity of a session ticket.

DELETE

/tickets/{tgt}

Log out a customer.

GET

/tickets/{tgt}/serviceTicket

Obtains a one-time Service Ticket that can be used to access other William Hill

POST

/tickets

Logs in a customer and obtains an authentication ticket.

GET

/tickets/{tgt}

Checks the validity of a session ticket.

DELETE

/tickets/{tgt}

Log out a customer.

GET

/tickets/{tgt}/serviceTicket

Obtains a one-time Service Ticket that can be used to access other William Hill

Why Jentic?

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

Credential isolation

This Sessions API declares no authentication in its spec, so there is no credential to store; if your instance later adds one, Jentic One stores it once, encrypted, and injects it at execution time so it never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'log in a customer and get a ticket' or 'get a service ticket', and Jentic returns the matching Sessions API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Sessions API through Jentic.

What authentication does the Sessions API use?

The Sessions API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I logs in a customer and obtains an authentication ticket. with the Sessions API?

Yes. Use the POST /tickets endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Sessions 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 logs in a customer and obtains an authentication ticket. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'logs in a customer and obtains an authentication ticket.'. Jentic returns the matching Sessions API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Sessions API have?

The Sessions API exposes 4 endpoints covering tickets operations.

Can I limit what my agent is allowed to do with the Sessions API?

Yes. Jentic One is self-hosted, so your own rules decide which Sessions API operations the agent may call and which credentials it may use. Because this API puts the ticket id in the URL path (/tickets/{tgt}), you can pin the agent to a single ticket and allow only reading that ticket (GET /tickets/{tgt}) or requesting its service ticket (GET /tickets/{tgt}/serviceTicket), while leaving out logout (DELETE /tickets/{tgt}) or login (POST /tickets) unless you explicitly add them.

Whapi Sessions API

Connect the Sessions API to your agent

Capabilities

Start building with Sessions API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs