Igtbdigital Account Master API

Name: Account Master API
Brand: Account Master API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlnone5 Endpoints

Install Jentic One Beta

Connect the Account Master API to your agent

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

To get the Accounts details

Delete Accounts Details

Adds new Account numbers to the system

Get all Accounts details

GET STARTED

Start building with Account Master API

Explore with Jentic

View OpenAPI Document

For Agents

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

Use for: I need to to get the accounts details, I want to accounts details, Search for adds new account numbers to the system, Find all all accounts details

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

Use Cases

Patterns agents use Account Master API for, with concrete tasks.

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

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.

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.

Search Jentic for 'to get the accounts details', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — this is a account master api.

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

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

Why Jentic?

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

Credential isolation

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.

Intent-based discovery

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.

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 Account Master API through Jentic.

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.