Session Manager API

Name: Session Manager API API
Brand: Session Manager API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthenticationapiKey4 EndpointsREST

For Agents

Programmatically create new session, get session. Covers 4 operations with apiKey authentication.

Connect the Session Manager API to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 Session Manager API API.

Create new session

Get session

Edit session

Query and filter Session Manager API records by parameters

Monitor Session Manager API operational status and events

GET STARTED

Start building with Session Manager API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Session Manager API, keeping it validated and agent-ready.

Session Manager tracks the current browsing sessions of all customers on the VTEX platform. Important session information is automatically captured and stored in a secure and easily accessible location. This includes data such as relevant cookies, query strings, authentication credentials, current profile and pricing information, if applicable. Session Manager API allows developers to retrieve and. The API exposes 4 endpoints secured with apiKey authentication.

Use Cases

Patterns agents use Session Manager API API for, with concrete tasks.

★ Identity and Authentication Operations

Use the Session Manager API to perform identity auth operations programmatically. The API provides 4 endpoints covering core functionality including create new session, get session, edit session.

Call POST /api/sessions to create new session

Automated Session Management

Automate session operations by combining multiple Session Manager API endpoints. Agents can get session and then edit session in a single workflow.

Call GET /api/sessions to get session, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Session Manager 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 'create new session', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

4 endpoints — session manager tracks the current browsing sessions of all customers on the vtex platform.

METHOD

PATH

DESCRIPTION

POST

/api/sessions

Create new session

GET

/api/sessions

Get session

PATCH

/api/sessions

Edit session

GET

/api/segments

Get segment

POST

/api/sessions

Create new session

GET

/api/sessions

Get session

PATCH

/api/sessions

Edit session

GET

/api/segments

Get segment

Why though Jentic?

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

Credential isolation

Session Manager API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create new session') and Jentic returns the matching Session Manager API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Session Manager API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Auth0

Alternative identity auth API

Choose Auth0 when you need a different approach to identity auth operations

Alternative

Okta

Alternative identity auth API

Choose Okta when you need a different approach to identity auth operations

FAQs

Specific to using Session Manager API API through Jentic.

What authentication does the Session Manager API use?

The Session Manager API uses an API key passed in the `vtex_session` cookie. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I create new session with the Session Manager API?

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

What are the rate limits for the Session Manager 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 create new session through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create new session'. Jentic returns the matching Session Manager API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Session Manager API have?

The Session Manager API exposes 4 endpoints covering session, segment operations.