Talon.One Integration API

Name: Talon.One Integration API
Brand: Talon.One Integration API
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthenticationapiKey8 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Talon.One Integration API to your agent

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

Update customer session

Get customer profile

Delete customer profile

Reserve coupon

GET STARTED

Start building with Talon.One Integration API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Talon.One Integration API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

8 endpoints — talon.

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

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

Why Jentic?

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

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Talon.One Integration API through Jentic.

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.

Talon.One Integration API

Connect the Talon.One Integration API to your agent

Capabilities

Start building with Talon.One Integration API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs