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

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.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
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

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Finance / Codat / Bank Feeds
Bank Feeds logo

Codat Bank Feeds

Browse all Codat APIs
53
AI ReadinessFoundational (C)53/100
See full scorecard
Official vendor OpenAPI document · agent-readyFinanceBankingapiKey32 EndpointsREST

For Agents

Push bank transactions from a financial institution or fintech platform directly into a customer's accounting software as a native bank feed.

Use for: I want to set up a bank feed from a customer's bank account to QuickBooks, Push today's bank transactions into the customer's Xero ledger, Map a source bank account to a target chart-of-accounts entry, Check whether the last sync to the accounting platform succeeded

Not supported: Does not handle reading the accounting ledger, payment processing, or direct bank account aggregation - use for posting bank transactions into a customer's accounting platform as a native bank feed only.

Codat's Bank Feeds API lets banks, neobanks, and spend management platforms push transaction data directly into a customer's accounting software as a native bank feed. It manages company and connection lifecycle, source-to-target account mapping, sync configuration, and transaction posting so an end-customer's QuickBooks, Xero, or Sage automatically receives the bank's transactions without CSV imports. The API also exposes sync status endpoints so platforms can monitor whether each daily push reached the destination ledger.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Bank Feeds to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bank Feeds, 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%2Fcodat.io%2Fbank-feeds" | 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%2Fcodat.io%2Fbank-feeds" | 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 Feeds API.

Provision a Bank Feeds connection between a bank account and a customer's accounting platform

Map source bank accounts to target ledger accounts in QuickBooks, Xero, or Sage

Post bank transactions to the customer's accounting software via the configured feed

Trigger and monitor scheduled syncs to confirm transactions reached the destination ledger

Manage company and connection records so platforms can track each end-customer's feed

Configure feed-level settings such as currency, source account, and posting cadence

Retrieve company information and authorisation tokens needed for hosted bank feed onboarding

Use Cases

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

★ Bank-Owned Accounting Bank Feed

Banks and neobanks use the Bank Feeds API to deliver bank transactions to small business customers' accounting software as a native feed, branded as the bank's own integration. The /companies/{companyId}/sync/banking/config and /sync/banking endpoints handle configuration and posting so the bank can offer same-day reconciliation in QuickBooks or Xero without building per-platform connectors.

Create a bank-feeds connection for company {companyId}, map source account {sourceId} to target ledger account, and run an initial sync.

Spend Management Reconciliation

Spend management and corporate card platforms use Bank Feeds to write the platform's own transactions into the customer's accounting ledger. Instead of asking finance teams to import CSVs, the platform posts each transaction through the configured feed so they appear in the customer's QuickBooks or Xero bank-feed view ready for matching against bills.

Post a batch of 50 card transactions for company {companyId} to the configured bank feed and confirm the sync status reached 'Success'.

Embedded Finance Treasury Visibility

Embedded finance providers running treasury or operating-account products use Bank Feeds so customers see their balance and transactions inside their existing accounting software. The /companies/{companyId}/connections endpoints manage connection lifecycle and the /sync/banking/syncs/lastSuccessful/status endpoint lets the platform display feed health back to the customer.

List all bank-feeds connections for company {companyId}, then fetch the last successful sync status for each.

AI Agent Sync Monitor

AI agents that monitor finance integrations use Bank Feeds through Jentic to detect failed syncs and remediate them. The agent searches Jentic for 'check bank feed sync status', loads the operation, and polls /sync/banking/syncs/lastSuccessful/status across companies, raising tickets when a sync has not completed in 24 hours. Jentic handles credential isolation so the Codat API key never enters the agent runtime.

Search Jentic for 'last successful bank feed sync', load the operation, and report any company where the last sync is older than 24 hours.

Key Endpoints

32 endpoints — codat's bank feeds api lets banks, neobanks, and spend management platforms push transaction data directly into a customer's accounting software as a native bank feed.

METHOD

PATH

DESCRIPTION

POST

/companies

Create a company record for a bank-feed customer

POST

/companies/{companyId}/connections

Create a connection to the target accounting platform

GET

/companies/{companyId}/connections/{connectionId}/data/bankAccounts

List bank accounts visible to the connection

GET

/companies/{companyId}/sync/banking/config

Retrieve the current bank-feed sync configuration

GET

/companies/{companyId}/sync/banking/syncs/lastSuccessful/status

Check the status of the most recent successful sync

POST

/companies

Create a company record for a bank-feed customer

POST

/companies/{companyId}/connections

Create a connection to the target accounting platform

GET

/companies/{companyId}/connections/{connectionId}/data/bankAccounts

List bank accounts visible to the connection

GET

/companies/{companyId}/sync/banking/config

Retrieve the current bank-feed sync configuration

GET

/companies/{companyId}/sync/banking/syncs/lastSuccessful/status

Check the status of the most recent successful sync

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

B

Bank Feeds

- Foundational (C)
53/100
49
Foundational Compliance
74
Developer Experience & Jentic Compatibility
33
AI-Readiness & Agent Experience
94
Agent Usability
50
Security
74
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
49

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4
72%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

25%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

74

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4
22%

Example Density

How richly the API is illustrated with examples.

99%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

33

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
29%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

97%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

7%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

50

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1
50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

74

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1
74%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

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

Setup

Wiring Codat Bank Feeds by hand means building its Basic API-key header, targeting api.codat.io, and managing company creation, connection setup, and sync-status polling yourself. Through Jentic you install once, import Bank Feeds from the API Directory, store the Codat API key once, and your agent calls it.

Permission scoping

Bank Feeds puts the company id in the URL path (/companies/{companyId}/connections/... and /companies/{companyId}/sync/banking/...), so a rule can pin your agent to one company: it manages that company's bank-feed connections and reads its sync status and nothing else. You choose the operations it may call, so creating new connections is only in the allowed set if you add it.

Credential isolation

Your Codat API key is stored once, encrypted, by your own Jentic One instance and injected at execution time as the Basic Authorization header. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'post bank transactions to accounting software' or 'check the last successful banking sync', and Jentic returns the matching Bank Feeds 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

Codat Banking API

→

Reads bank data from connected accounts rather than pushing transactions into accounting platforms

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

Complementary

Codat Accounting API

→

Provides full read and write access to the accounting ledger that Bank Feeds posts into

Use Accounting when the agent needs ledger-wide read or write; use Bank Feeds for the narrow task of posting bank transactions as a native feed.

Complementary

Codat Sync for Expenses

→

Pushes expense transactions and receipts into accounting platforms

Use Sync for Expenses when the agent needs to write expense-style transactions; use Bank Feeds when posting raw bank-feed transactions.

FAQs

Specific to using Bank Feeds API through Jentic.

What authentication does the Codat Bank Feeds 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, so the agent never sees the raw key.

Can I post transactions into QuickBooks with the Bank Feeds API?

Yes. After creating a connection and mapping source accounts to target ledger accounts, post transactions via the bank-feeds transactions endpoints under /companies/{companyId}. Transactions then appear in the customer's QuickBooks bank-feed view ready to match against bills and invoices.

What are the rate limits for the Codat Bank Feeds 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 destination accounting platform's own limits. Codat returns HTTP 429 with a Retry-After header when limits are hit and recommends exponential backoff for retries.

How do I check whether a bank-feed sync succeeded through Jentic?

Search Jentic for 'last successful bank feed sync', load the GET /companies/{companyId}/sync/banking/syncs/lastSuccessful/status operation, and execute it with the company ID. Install with pip install jentic and use the standard async search, load, and execute flow.

Which accounting platforms does the Bank Feeds API support?

Codat's Bank Feeds product supports QuickBooks Online, Xero, and Sage as primary destinations, with the same endpoint surface used regardless of target platform. The /companies/{companyId}/connections call selects the target during connection creation.

Can I map multiple source bank accounts to one accounting ledger account?

Yes. The /companies/{companyId}/connections/{connectionId}/sync/banking endpoints expose source-to-target account mapping so multiple source accounts can feed into a single target account in the customer's chart of accounts, depending on the destination platform's rules.

Can I limit what my agent is allowed to do with the Codat Bank Feeds API?

Yes. Because you run Jentic One yourself, your own rules decide which Bank Feeds operations and credentials the agent may use. Since the company id sits in the URL path (/companies/{companyId}/connections/... and /companies/{companyId}/sync/banking/...), you can pin the agent to a single company so it only manages that company's connections and reads its sync status. You also pick the exact operations it may call, so a write like creating a new connection is available only if you add it to the allowed set, and the Codat API key stays with your instance rather than the agent.

GET STARTED

Start building with Bank Feeds API

Explore with Jentic One
View OpenAPI Document