canonical: https://jentic.com/apis/swaggerhub.igtbdigital/wallet-action-apis

# Igtbdigital Wallet Action APIs

Wallet catalog is basically an feature containing different wallet types.Helps in carrying various task and services. The API exposes 4 endpoints.

## For AI agents

Programmatically draft / initiate to create a wallet, draft / initiate to update existing wallet.. Covers 4 operations.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Draft / Initiate to Create a wallet
- Update Wallet Request Status
- Integrate Wallet Action APIs into automated workflows
- Query and filter Wallet Action APIs records by parameters
- Monitor Wallet Action APIs operational status and events

## Use cases

### E-Commerce Operations

Use the Wallet Action APIs to perform e commerce operations programmatically. The API provides 4 endpoints covering core functionality including draft / initiate to create a wallet, draft / initiate to update existing wallet., draft / initiate to delete existing wallet.

Example prompt: Call POST /v1/wallets to draft / initiate to create a wallet

### Automated Wallet Management

Automate wallet operations by combining multiple Wallet Action APIs endpoints. Agents can draft / initiate to update existing wallet. and then draft / initiate to delete existing wallet in a single workflow.

Example prompt: Call PUT /v1/wallets/{walletId} to draft / initiate to update existing wallet., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Wallet Action APIs 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 none tokens manually.

Example prompt: Search Jentic for 'draft / initiate to create a wallet', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v1/wallets | Draft / Initiate to Create a wallet |
| PUT | /v1/wallets/{walletId} | Draft / Initiate to Update existing Wallet. |
| DELETE | /v1/wallets/{walletId} | Draft / Initiate to Delete existing Wallet |
| PUT | /v1/wallets/{channelSeqId}/state | Update Wallet Request Status |

## Key resources

- **Wallet** — APIs to manage Wallet catalog of different Wallet type which includes beneficiary, customer, Service

## Why Jentic

- **Setup:** Wiring the Wallet Action APIs by hand means pointing at their SwaggerHub-hosted mock server, tracking the version in the base path, and handling the wallet request and state shapes yourself. Through Jentic you install once, import the Wallet Action APIs from the API Directory, and your agent calls it.
- **Permission scoping:** The API puts the wallet id in the URL path (/v1/wallets/{walletId}), so a rule can pin your agent to one wallet: it can update that wallet and nothing else. You choose the operations it may call, so destructive ones like wallet deletion or the state change are not included unless you add them.
- **Credential handling:** This API declares no authentication, so there is no secret to pass. If the live endpoint later requires a credential, it is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a wallet' or 'update a wallet', and Jentic returns the matching Wallet Action APIs operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Wallet Action APIs use?

The Wallet Action APIs uses no authentication. 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 draft / initiate to create a wallet with the Wallet Action APIs?

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

### What are the rate limits for the Wallet Action APIs?

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 draft / initiate to create a wallet through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'draft / initiate to create a wallet'. Jentic returns the matching Wallet Action APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Wallet Action APIs have?

The Wallet Action APIs exposes 4 endpoints covering wallet operations.

### Can I limit what my agent is allowed to do with the Wallet Action APIs?

Yes. Because you run Jentic One yourself, your own rules decide which of the four operations the agent may call, so you can grant read or update access while withholding destructive ones like DELETE /v1/wallets/{walletId} or the state change on /v1/wallets/{channelSeqId}/state. Since the wallet id sits in the URL path (/v1/wallets/{walletId}), a rule can pin the agent to a single wallet, letting it update that wallet and nothing else. The operator controls the operations and credentials the agent is permitted to use.