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

# Igtbdigital Account Master API

This is a Account Master API. The API exposes 5 endpoints.

## For AI agents

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

## Scope

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

## Capabilities

- To get the Accounts details
- Delete Accounts Details
- Adds new Account numbers to the system
- Get all Accounts details
- Update Account Details

## Use cases

### Developer Tools Operations

Use the Account Master API to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including to get the accounts details, delete accounts details, adds new account numbers to the system.

Example prompt: Call GET /v1/common/accounts/{accountNo}/{bankEntityId} to to get the accounts details

### Automated Account Master Management

Automate account master operations by combining multiple Account Master API endpoints. Agents can delete accounts details and then adds new account numbers to the system in a single workflow.

Example prompt: Call DELETE /v1/common/accounts/{accountNo}/{bankEntityId} to delete accounts details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Account Master API 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 accounts details', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/common/accounts/{accountNo}/{bankEntityId} | To get the Accounts details |
| DELETE | /v1/common/accounts/{accountNo}/{bankEntityId} | Delete Accounts Details |
| POST | /v1/common/accounts | Adds new Account numbers to the system |
| GET | /v1/common/accounts | Get all Accounts details |
| PUT | /v1/common/accounts | Update Account Details |

## Key resources

- **Account Master** — It contains Accounts Details

## Why Jentic

- **Setup:** Wiring the Account Master API by hand means pointing at its SwaggerHub-hosted mock server, tracking the version in the base path, and handling the account request shapes yourself. Through Jentic you install once, import the Account Master API from the API Directory, and your agent calls it.
- **Permission scoping:** The API puts the account number and bank entity id in the URL path (/v1/common/accounts/{accountNo}/{bankEntityId}), so a rule can pin your agent to one account: it can read that account and nothing else. You choose the operations it may call, so destructive ones like account deletion 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 'get an account by number and bank entity', and Jentic returns the matching Account Master API 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 Account Master API use?

The Account Master API 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 accounts details with the Account Master API?

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

### What are the rate limits for the Account Master API?

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 accounts 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 accounts details'. Jentic returns the matching Account Master API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Account Master API have?

The Account Master API exposes 5 endpoints covering account master operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Account Master API operations and credentials the agent can use. Since the account number and bank entity id sit in the URL path (/v1/common/accounts/{accountNo}/{bankEntityId}), you can pin the agent to a single account so it reads that account and nothing else. You also choose which operations it may call, so destructive ones like DELETE /v1/common/accounts/{accountNo}/{bankEntityId} stay out of reach unless you explicitly allow them.