canonical: https://jentic.com/apis/swaggerhub.pgaldamez/api-visanet-ecommerce

# Pgaldamez API Visanet eCommerce

API encargada de la operatividad via comercio electronico. The API exposes 12 endpoints secured with apiKey authentication.

## For AI agents

Programmatically remove card token, remove card token. Covers 12 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Remove Card Token
- Retrieve Token List
- Get Client Ip
- Query Session Token
- Create Session Token

## Use cases

### Developer Tools Operations

Use the API Visanet eCommerce to perform developer tools operations programmatically. The API provides 12 endpoints covering core functionality including remove card token, remove card token, retrieve token list.

Example prompt: Call POST /card/management/remove/{vault} to remove card token

### Automated API to get client Ip Management

Automate API to get client ip operations by combining multiple API Visanet eCommerce endpoints. Agents can remove card token and then retrieve token list in a single workflow.

Example prompt: Call POST /card/management/remove/{vault}/{block}/{attribute} to remove card token, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API Visanet eCommerce 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 'remove card token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /card/management/remove/{vault} | Remove Card Token |
| POST | /card/management/remove/{vault}/{block}/{attribute} | Remove Card Token |
| GET | /card/management/retrieve/{vault}/{block} | Retrieve Token List |
| GET | /clientip | Get Client Ip |
| GET | /configuration/merchant/{entityId} | Retrieve Merchant Configuration |
| GET | /ecommerce/token/query/{merchant}/{transactionToken}/{amount} | Query Session Token |
| POST | /ecommerce/token/session/{entityId} | Create Session Token |
| POST | /ecommerce/token/transaction | Create Transaction Token |

## Key resources

- **Api to get client Ip** — Api to get client Ip
- **Api to manage tokenized cards** — Api which manage tokenized cards
- **Card Bin Additional Information** — Query in order to retrieve card bin additional information
- **Create Session Token** — RESTful API to create a session token.
- **Manage Session Time** — RESTful API to manage session time

## Why Jentic

- **Setup:** Wiring API Visanet eCommerce by hand means passing the access token in the Authorization header, threading vault, entity, and merchant ids through each path, and handling the card, token, and session responses yourself. Through Jentic you install once, import API Visanet eCommerce from the API Directory, store the access token once, and your agent calls it.
- **Permission scoping:** API Visanet eCommerce puts the vault and entity id in the URL path (/card/management/retrieve/{vault}/{block}, /configuration/merchant/{entityId}), so a rule can pin your agent to one vault or merchant and nothing else. You choose the operations it may call, so a destructive one like removing a stored card is not included unless you add it.
- **Credential handling:** Your API Visanet eCommerce access token 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 'create a payment session' or 'query a card token', and Jentic returns the matching API Visanet eCommerce operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the API Visanet eCommerce use?

The API Visanet eCommerce 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 remove card token with the API Visanet eCommerce?

Yes. Use the POST /card/management/remove/{vault} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the API Visanet eCommerce?

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 remove card token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'remove card token'. Jentic returns the matching API Visanet eCommerce operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the API Visanet eCommerce have?

The API Visanet eCommerce exposes 12 endpoints covering API to get client ip, API to manage tokenized cards, card bin additional information operations.

### Can I limit what my agent is allowed to do with the API Visanet eCommerce?

Yes. Jentic One is self-hosted by you, so your own rules decide which API Visanet eCommerce operations and credentials the agent may use. Because the API puts the vault and entity id in the URL path, such as /card/management/retrieve/{vault}/{block} and /configuration/merchant/{entityId}, you can pin the agent to a single vault or merchant and nothing else. You also choose the operations it may call, so a destructive one like POST /card/management/remove/{vault} is excluded unless you add it.