Product
Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing
Developers

GET STARTED

API DirectoryBrowse 10,000+ APIs Ready For AI Agent IntegrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI Readiness using our scorecardArazzo UIVisualize Arazzo Workflows As Interactive DocumentationArazzo EditorBuild And Edit Multi-Step API Workflows Visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
Resources
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
Resources
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
Switch to light modeSwitch to dark mode
APIs / Finance / Swaggerhub Igtbdigital / Bank Master
Bank Master logo

Igtbdigital Bank Master

Browse all Swaggerhub Igtbdigital APIs
Community OpenAPI document · agent-readyFinanceBankingnone5 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to to get the bank details, I want to bank details, Search for adds new banks to the system, Find all all bank details

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

It contains Bank Details. The API exposes 5 endpoints.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Bank Master to your agent

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

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.igtbdigital%2Fbank-master" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.igtbdigital%2Fbank-master" | 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 Bank Master API.

To get the Bank Details

Delete Bank Details

Adds new banks to the system

Get all bank details

Update Bank Details

Use Cases

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

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

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.

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.

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

Key Endpoints

5 endpoints — it contains bank details.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

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

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 management

Credential isolation

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.

Intent-based discovery

Intent-based discovery

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

Alternatives and complements available in the Jentic catalogue.

Alternative

Plaid

→

Alternative finance API

Choose Plaid when you need a different approach to finance operations

Alternative

Xero

→

Alternative finance API

Choose Xero when you need a different approach to finance operations

FAQs

Specific to using Bank Master API through Jentic.

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.

GET STARTED

Start building with Bank Master API

Explore with Jentic One
View OpenAPI Document