canonical: https://jentic.com/apis/swaggerhub.igtbdigital/bank-master

# Igtbdigital Bank Master

It contains Bank Details. The API exposes 5 endpoints.

## For AI agents

Programmatically to get the bank details, delete bank details. Covers 5 operations.

## Scope

Does not handle payments, communications, or crm - use for finance and accounting only.

## Capabilities

- To get the Bank Details
- Delete Bank Details
- Adds new banks to the system
- Get all bank details
- Update Bank Details

## Use cases

### Finance and Accounting Operations

Use the Bank Master to perform finance operations programmatically. The API provides 5 endpoints covering core functionality including to get the bank details, delete bank details, adds new banks to the system.

Example prompt: Call GET /v1/common/banks/{bankCode} to to get the bank details

### Automated Bank Master Management

Automate bank master operations by combining multiple Bank Master endpoints. Agents can delete bank details and then adds new banks to the system in a single workflow.

Example prompt: Call DELETE /v1/common/banks/{bankCode} to delete bank details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Bank Master 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 'to get the bank details', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/common/banks/{bankCode} | To get the Bank Details |
| DELETE | /v1/common/banks/{bankCode} | Delete Bank Details |
| POST | /v1/common/banks | Adds new banks to the system |
| GET | /v1/common/banks | Get all bank details |
| PUT | /v1/common/banks | Update Bank Details |

## Key resources

- **Bank Master** — It contains Bank Details

## Why Jentic

- **Setup:** Wiring the Bank Master API by hand means reading its spec, building CRUD calls for the bank records, and handling request formatting and retries yourself. Through Jentic you install once, import Bank Master from the API Directory, store any required connection detail once, and your agent calls it.
- **Permission scoping:** Bank Master puts the bank code in the URL path (/v1/common/banks/{bankCode}), so a rule can pin your agent to reading one bank. You choose the operations it may call, so write operations like creating, updating, or deleting a bank are not included unless you add them.
- **Credential handling:** Any connection detail the Bank Master API needs 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 'get the details for a bank code', and Jentic returns the matching Bank Master operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Plaid** — Alternative finance API
- **Xero** — Alternative finance API

## FAQ

### What authentication does the Bank Master use?

The Bank Master 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 to get the bank details with the Bank Master?

Yes. Use the GET /v1/common/banks/{bankCode} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Bank Master?

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 to get the bank details through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'to get the bank details'. Jentic returns the matching Bank Master operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Bank Master have?

The Bank Master exposes 5 endpoints covering bank master operations.

### Can I limit what my agent is allowed to do with the Bank Master API?

Yes. Because you run Jentic One yourself, your own rules decide which Bank Master operations and credentials the agent may use. The Bank Master API puts the bank code in the URL path (/v1/common/banks/{bankCode}), so you can pin the agent to reading a single bank with GET /v1/common/banks/{bankCode} while withholding the write operations, meaning POST /v1/common/banks, PUT /v1/common/banks, and DELETE /v1/common/banks/{bankCode} stay off limits unless you add them. The agent can only call the operations you have granted.