License Manager API

Name: License Manager API API
Brand: License Manager API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsEmail DeliveryapiKey13 EndpointsREST

For Agents

Programmatically get user, delete user. Covers 13 operations with apiKey authentication.

Connect the License Manager API to your agent

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

Get user

Delete user

Create user

Add roles to user or appKey

Remove role from user or appKey

GET STARTED

Start building with License Manager API API

Explore with Jentic

View OpenAPI Document

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

The License Manager API allows you to create users, modify their names and emails, add and remove [roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) from users, and create and manage [appKeys](https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet). Common parameters |Attribute name | Description | |:------------|--------------| |`accountName` | Account na. The API exposes 13 endpoints secured with apiKey authentication.

Use Cases

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

★ Communications Operations

Use the License Manager API to perform communications operations programmatically. The API provides 13 endpoints covering core functionality including get user, delete user, create user.

Call GET /api/license-manager/users/{userId} to get user

Automated Users Management

Automate users operations by combining multiple License Manager API endpoints. Agents can delete user and then create user in a single workflow.

Call DELETE /api/license-manager/users/{userId} to delete user, then verify the result

AI Agent Integration via Jentic

AI agents discover and call License 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 'get user', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

13 endpoints — the license manager api allows you to create users, modify their names and emails, add and remove [roles](https://help.

METHOD

PATH

DESCRIPTION

GET

/api/license-manager/users/{userId}

Get user

DELETE

/api/license-manager/users/{userId}

Delete user

POST

/api/license-manager/users

Create user

GET

/api/license-manager/site/pvt/logins/list/paged

Get list of users

GET

/api/license-manager/users/{userId}/roles

Get roles by user or appKey

PUT

/api/license-manager/users/{userId}/roles

Add roles to user or appKey

DELETE

/api/license-manager/users/{userId}/roles/{roleId}

Remove role from user or appKey

GET

/api/license-manager/site/pvt/roles/list/paged

Get list of roles

GET

/api/license-manager/users/{userId}

Get user

DELETE

/api/license-manager/users/{userId}

Delete user

POST

/api/license-manager/users

Create user

GET

/api/license-manager/site/pvt/logins/list/paged

Get list of users

GET

/api/license-manager/users/{userId}/roles

Get roles by user or appKey

Why though Jentic?

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

Credential isolation

License 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., 'get user') and Jentic returns the matching License Manager API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct License 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

Twilio

Alternative communications API

Choose Twilio when you need a different approach to communications operations

Alternative

Sendgrid

Alternative communications API

Choose Sendgrid when you need a different approach to communications operations

Complementary

Pusher

Complementary communications API

Choose Pusher when you need a complementary approach to communications operations

FAQs

Specific to using License Manager API API through Jentic.

What authentication does the License Manager API use?

The License Manager API uses an API key passed in the `X-VTEX-API-AppKey` header. 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 get user with the License Manager API?

Yes. Use the GET /api/license-manager/users/{userId} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the License 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 get user through Jentic?

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

How many endpoints does the License Manager API have?

The License Manager API exposes 13 endpoints covering users, app keys, roles operations.