canonical: https://jentic.com/apis/talon.one/talon-one

# Talon.One Integration API

Talon.One Integration API for managing customer sessions, loyalty, coupons, and campaign effects in real-time. The API exposes 8 endpoints secured with apiKey authentication.

## For AI agents

Programmatically update customer session, get customer profile. Covers 8 operations with apiKey authentication.

## Scope

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

## Capabilities

- Update customer session
- Get customer profile
- Delete customer profile
- Reserve coupon
- Release coupon reservation
- Track event

## Use cases

### Identity and Authentication Operations

Use the Talon.One Integration API to perform identity auth operations programmatically. The API provides 8 endpoints covering core functionality including update customer session, get customer profile, update customer profile.

Example prompt: Call PUT /v2/customer_sessions/{customerSessionId} to update customer session

### Automated Coupon_Reservations Management

Automate coupon_reservations operations by combining multiple Talon.One Integration API endpoints. Agents can get customer profile and then update customer profile in a single workflow.

Example prompt: Call GET /v2/customer_profiles/{integrationId} to get customer profile, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Talon.One Integration 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 apiKey tokens manually.

Example prompt: Search Jentic for 'update customer session', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| PUT | /v2/customer_sessions/{customerSessionId} | Update customer session |
| GET | /v2/customer_profiles/{integrationId} | Get customer profile |
| PUT | /v2/customer_profiles/{integrationId} | Update customer profile |
| DELETE | /v2/customer_profiles/{integrationId} | Delete customer profile |
| POST | /v1/coupon_reservations/{couponValue} | Reserve coupon |
| DELETE | /v1/coupon_reservations/{couponValue} | Release coupon reservation |
| POST | /v2/events | Track event |
| POST | /v1/customer_profiles/{integrationId}/audiences | Update audience membership |

## Key resources

- **Coupon_Reservations** — Operations for coupon_reservations
- **Customer_Profiles** — Operations for customer_profiles
- **Customer_Sessions** — Operations for customer_sessions
- **Events** — Operations for events

## Why Jentic

- **Setup:** Wiring the Talon.One Integration API by hand means sending its API key in the Authorization header on every call and threading integration, session, and coupon ids through the right routes yourself. Through Jentic you install once, import the Talon.One Integration API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Talon.One puts the integration id in the URL path (/v2/customer_profiles/{integrationId}), so a rule can pin your agent to one customer profile: it can read that profile and nothing else. You choose the operations it may call, so updating or deleting a profile is not included unless you add it.
- **Credential handling:** Your Talon.One key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'update a customer session' or 'reserve a coupon', and Jentic returns the matching Talon.One operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Talon.One Integration API use?

The Talon.One Integration API uses an API key passed in the `Authorization` header. 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 update customer session with the Talon.One Integration API?

Yes. Use the PUT /v2/customer_sessions/{customerSessionId} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Talon.One Integration 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 update customer session through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'update customer session'. Jentic returns the matching Talon.One Integration API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Talon.One Integration API have?

The Talon.One Integration API exposes 8 endpoints covering coupon_reservations, customer_profiles, customer_sessions operations.

### Can I limit what my agent is allowed to do with the Talon.One Integration API?

Yes. Because your Jentic One instance is self-hosted, your own rules decide which Talon.One operations and credentials the agent may use. Since the integration id sits in the URL path such as /v2/customer_profiles/{integrationId}, a rule can pin the agent to a single customer profile so it can read that profile and nothing else. You choose the operations it may call, so updating a session, deleting a profile, or reserving a coupon stays off limits unless you explicitly allow it.