For Agents
Programmatically remove card token, remove card token. Covers 24 operations with apiKey authentication.
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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# 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 instanceJentic 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.
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
Use for: I need to remove card token, I want to remove card token, Search for token list, Find all token list
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
Jentic publishes the only available OpenAPI document for API Niubiz eCommerce, keeping it validated and agent-ready.
Api encargada de la operatividad via comercio electronico. The API exposes 24 endpoints secured with apiKey authentication.
Monitor API Niubiz eCommerce operational status and events
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
24 endpoints — api encargada de la operatividad via comercio electronico.
METHOD
PATH
DESCRIPTION
/card/management/remove/{vault}
Remove Card Token
/card/management/remove/{vault}/{block}/{attribute}
Remove Card Token
/card/management/retrieve/filter/{vault}/eblock/{block}
Retrieve Token List
/card/management/retrieve/filter/{vault}/{block}
Retrieve Token List
/card/management/retrieve/{vault}/eblock/{block}
Retrieve Token List
/card/management/retrieve/{vault}/{block}
Retrieve Token List
/clientip
Get Client Ip
/configuration/merchant/management/{entityId}
Create/Update Merchant Configuration
/card/management/remove/{vault}
Remove Card Token
/card/management/remove/{vault}/{block}/{attribute}
Remove Card Token
/card/management/retrieve/filter/{vault}/eblock/{block}
Retrieve Token List
/card/management/retrieve/filter/{vault}/{block}
Retrieve Token List
/card/management/retrieve/{vault}/eblock/{block}
Retrieve Token List
Three things that make agents converge on Jentic-routed access.
Credential isolation
API Niubiz eCommerce 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., 'remove card token') and Jentic returns the matching API Niubiz eCommerce operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct API Niubiz eCommerce integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Gitlab
Alternative developer tools API
Choose Gitlab when you need a different approach to developer tools operations
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
/card/management/retrieve/{vault}/{block}
Retrieve Token List
/clientip
Get Client Ip
/configuration/merchant/management/{entityId}
Create/Update Merchant Configuration