Visanetperu API Niubiz eCommerce

Name: API Niubiz eCommerce API
Brand: API Niubiz eCommerce
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource ControlapiKey24 Endpoints

Install Jentic One Beta

Connect the API Niubiz eCommerce to your agent

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

Remove Card Token

Retrieve Token List

Get Client Ip

Query and filter API Niubiz eCommerce records by parameters

GET STARTED

Start building with API Niubiz eCommerce API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use API Niubiz eCommerce API for, with concrete tasks.

★ Developer Tools Operations

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

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 Niubiz eCommerce endpoints. Agents can remove card token and then retrieve token list in a single workflow.

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

Search Jentic for 'remove card token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

24 endpoints — api encargada de la operatividad via comercio electronico.

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/filter/{vault}/eblock/{block}

Retrieve Token List

GET

/card/management/retrieve/filter/{vault}/{block}

Retrieve Token List

GET

/card/management/retrieve/{vault}/eblock/{block}

Retrieve Token List

GET

/card/management/retrieve/{vault}/{block}

Retrieve Token List

GET

/clientip

Get Client Ip

POST

/configuration/merchant/management/{entityId}

Create/Update Merchant Configuration

POST

/card/management/remove/{vault}

Remove Card Token

POST

/card/management/remove/{vault}/{block}/{attribute}

Remove Card Token

GET

/card/management/retrieve/filter/{vault}/eblock/{block}

Retrieve Token List

GET

/card/management/retrieve/filter/{vault}/{block}

Retrieve Token List

GET

/card/management/retrieve/{vault}/eblock/{block}

Retrieve Token List

Why Jentic?

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

Credential isolation

Your Niubiz 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.

Intent-based discovery

Agents search Jentic by intent such as 'retrieve a stored card token from a vault' or 'get the client IP', and Jentic returns the matching API Niubiz eCommerce operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using API Niubiz eCommerce API through Jentic.

What authentication does the API Niubiz eCommerce use?

The API Niubiz 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 Niubiz 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 Niubiz 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 Niubiz eCommerce operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the API Niubiz eCommerce have?

The API Niubiz eCommerce exposes 24 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 Niubiz eCommerce?

Yes. Because you self-host Jentic One, your own rules decide which API Niubiz eCommerce operations and credentials the agent may use, so you can allow a read-only path like GET /card/management/retrieve/{vault}/{block} while withholding a destructive one such as POST /card/management/remove/{vault}. Since the vault id sits in the URL path, a rule can pin the agent to a single vault, letting it retrieve stored card blocks only for that vault. The agent can reach an operation only when you add it to the allowed set, and the Niubiz access token stays encrypted in your own instance and is injected at execution time rather than exposed to the agent.