Banking API

Name: Banking API API
Brand: Banking API
Availability: InStock

✓ Official Vendor SpecFinanceBankingapiKey8 EndpointsREST

For Agents

Read bank accounts, balances, and categorised transactions from a customer's linked bank account for cash flow analysis and credit decisioning.

Connect the Banking API to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 Banking API API.

Retrieve a customer's linked bank accounts with account name, currency, and identifier

Read current and historical balances for each linked bank account

Pull categorised bank transactions including merchant, amount, date, and assigned category

List transaction categories used to classify spending and inflows

GET STARTED

Start building with Banking API API

Explore with Jentic

View OpenAPI Document

Use for: I want to read a borrower's bank transactions for the last 90 days, Get the current balance on a customer's connected bank account, List all bank accounts linked to a company, Retrieve categorised bank transactions for cash flow analysis

Not supported: Does not handle posting transactions into accounting software, payment initiation, or accounting ledger reads — use for reading bank account, balance, and categorised transaction data from linked banking sources only.

Use Cases

Patterns agents use Banking API API for, with concrete tasks.

★ Cash Flow Underwriting

Lenders use the Codat Banking API to verify a borrower's cash flow directly from their bank. The /companies/{companyId}/connections/{connectionId}/data/banking-transactions and /banking-accountBalances endpoints provide categorised transactions and balances so credit models can score volatility, recurring income, and overdraft frequency without asking applicants to upload statements.

Fetch the last 90 days of categorised bank transactions for company {companyId} connection {connectionId} and compute total inflow versus outflow.

Bookkeeping Automation

Bookkeeping platforms read bank transactions through the Banking API to suggest matches against unreconciled invoices and bills in the customer's accounting software. The /banking-transactions endpoint plus the /banking-transactionCategories list let the platform group similar transactions and propose categorisations to the bookkeeper for one-click approval.

Pull all bank transactions for company {companyId} since the last reconciliation date and group them by category.

SMB Cash Flow Forecasting

B2B SaaS products that build SMB cash flow forecasts use Banking API balance and transaction history as the input series. The /banking-accounts and /banking-accountBalances endpoints give the current state, and the /banking-transactions endpoint with date filtering supplies the trailing data the forecast model needs.

Retrieve account balances and the last 12 months of transactions for company {companyId} and return a daily ending-balance series.

AI Agent Credit Analyst

AI agents acting as credit analysts use the Codat Banking API through Jentic to assemble the bank-data section of a credit memo. The agent searches Jentic for 'list banking transactions', loads the schema, and pulls categorised transactions and balances. Jentic isolates the Codat API key in its vault, and the unified search means the agent does not have to know the exact Codat path structure.

Search Jentic for 'banking transactions codat', load the operation, then pull the last 12 months of transactions for company {companyId} and summarise the largest five outflows.

Key Endpoints

8 endpoints — codat's banking api surfaces bank account, balance, transaction, and transaction-category data from a customer's directly-linked bank or open-banking provider.

METHOD

PATH

DESCRIPTION

GET

/companies/{companyId}/connections/{connectionId}/data/banking-accounts

List linked bank accounts for a connection

GET

/companies/{companyId}/connections/{connectionId}/data/banking-accountBalances

Read account balances

GET

/companies/{companyId}/connections/{connectionId}/data/banking-transactions

List categorised bank transactions

GET

/companies/{companyId}/data/banking-transactions

List transactions aggregated across all connections for a company

GET

/companies/{companyId}/connections/{connectionId}/data/banking-transactionCategories

List transaction categories

GET

/companies/{companyId}/connections/{connectionId}/data/banking-accounts

List linked bank accounts for a connection

GET

/companies/{companyId}/connections/{connectionId}/data/banking-accountBalances

Read account balances

GET

/companies/{companyId}/connections/{connectionId}/data/banking-transactions

List categorised bank transactions

GET

/companies/{companyId}/data/banking-transactions

List transactions aggregated across all connections for a company

GET

/companies/{companyId}/connections/{connectionId}/data/banking-transactionCategories

List transaction categories

Why though Jentic?

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

Credential isolation

Codat API keys are stored encrypted in the Jentic vault. Agents receive a scoped execution token; the 'Basic' Authorization header is constructed inside Jentic and never enters the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'list bank transactions for a borrower') and Jentic returns the matching Banking operation with its input schema, so the agent does not need to know the Codat path structure.

Time to first call

Direct Codat Banking integration: 3-7 days for auth and connection lifecycle. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Codat Bank Feeds

Pushes bank transactions into accounting software rather than reading them

Use Bank Feeds when the agent needs to write transactions into a customer's accounting platform; use Banking when the agent needs to read bank data.

Complementary

Codat Accounting API

Provides ledger-level invoices, bills, and journal entries to pair with raw banking data

Use Accounting alongside Banking when the agent needs both ledger and bank-level views for reconciliation or underwriting.

Complementary

Codat Assess API

Combines banking and accounting data into derived lending metrics

Use Assess when the agent needs ready-made underwriting metrics; use Banking when the agent needs raw transactions and balances.

FAQs

Specific to using Banking API API through Jentic.

What authentication does the Codat Banking API use?

The API uses an API key passed in the Authorization header as 'Basic <base64-encoded-key>'. The single security scheme in the spec is named auth_header. Through Jentic, the Codat API key is stored encrypted in the vault and the Authorization header is constructed inside Jentic at execution time.

Can I read categorised bank transactions with the Codat Banking API?

Yes. Use GET /companies/{companyId}/connections/{connectionId}/data/banking-transactions to list categorised transactions, and GET /companies/{companyId}/connections/{connectionId}/data/banking-transactionCategories to retrieve the category taxonomy. Both return data normalised by Codat from the underlying bank or open-banking source.

What are the rate limits for the Codat Banking API?

Codat does not publish a fixed rate limit in the OpenAPI spec; limits are governed at the company and connection level and depend on the underlying bank or open-banking provider. Codat returns HTTP 429 with a Retry-After header when limits are hit and recommends exponential backoff.

How do I pull bank balances through Jentic?

Search Jentic for 'bank account balances codat', load the GET /companies/{companyId}/connections/{connectionId}/data/banking-accountBalances operation, and execute it. Install with pip install jentic and use the standard async search, load, and execute flow.

Can I aggregate transactions across multiple connections for one company?

Yes. Use GET /companies/{companyId}/data/banking-transactions which returns transactions across every banking connection linked to the company, rather than scoping to a single connection. Use the connection-scoped endpoint when you need per-account isolation.