Which underlying platforms does Codat cover?

Codat normalises data from 20+ accounting platforms including QuickBooks, Xero, Sage, NetSuite, and FreeAgent, from commerce platforms including Shopify, Square, Stripe, Amazon, and eBay, and from linked bank and open-banking sources. The same endpoints and schemas work regardless of which underlying platform a customer uses.

Can agents both read and write financial data through Codat?

Yes, but the direction depends on the API. The Accounting API supports both reads and pushes, Bank Feeds, Sync for Commerce, and Sync for Expenses are write-oriented, and Banking, Commerce, and the reporting side of Assess are read-only. You scope which operations an agent may call based on the task.

Codat APIs for AI Agents

Q: When should I use Assess instead of the raw data APIs?

Use Assess when you need ready-made metrics for lending and underwriting, such as enhanced profit and loss, cash flow, MRR, customer retention, and data integrity scores. Use the Accounting, Banking, or Commerce APIs directly when you need the raw normalised records rather than derived figures.

FinanceAccountingBankingOfficial Vendor SpecsAPI keyAgent Ready

www.codat.io·Developer portal → docs.codat.io

Codat API Catalog

7 APIs across 2 product groups. All share one credential.

Finance5

Accounting APIRead and write standardised accounting data - invoices, bills, journal entries, customers, suppliers, and payments - across 20+ accounting platforms through a single unified interface.~135 endpoints Bank FeedsPush bank transactions from a financial institution or fintech platform directly into a customer's accounting software as a native bank feed.~32 endpoints Assess APIGenerate enhanced financial reports and lending metrics - enhanced P&L, balance sheet, cash flow, MRR, customer retention, and data integrity scores - from a customer's linked accounting and commerce data.~22 endpoints Sync for Expenses APIPush expense transactions from a card or spend management platform into a customer's accounting software with correct account, tax, and category mapping.~14 endpoints Banking APIRead bank accounts, balances, and categorised transactions from a customer's linked bank account for cash flow analysis and credit decisioning.~8 endpoints

E Commerce2

Sync for CommerceConfigure and trigger automated sync of a merchant's commerce sales, fees, and refunds into their accounting software, with integration branding and lifecycle controls.~22 endpoints Commerce APIRead normalised orders, payments, products, customers, and disputes from a merchant's connected commerce platform such as Shopify, Square, Stripe, or Amazon.~21 endpoints

Why Jentic?

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

Setup

Wiring Codat's APIs by hand means building a Basic API-key header, targeting api.codat.io, and threading company and connection IDs through paging and retries for every accounting, banking, commerce, and sync call. Through Jentic you install Jentic One once, add the Codat APIs you need from the Jentic directory, store the key once, and your agent calls any of them.

Permission scoping

Codat puts the company id in the URL path across every API, so your own rules in Jentic One can pin an agent to one company and to specific operations. You decide whether an agent gets read-only access to invoices, bank transactions, or commerce orders, or whether it may also push invoices, post bank feeds, or trigger expense syncs.

Credential isolation

FAQs

Specific to using Codat APIs through Jentic.

What can I do across Codat's APIs?

You can read normalised accounting, banking, and commerce data from a customer's linked platforms, write invoices, bills, bank feeds, expenses, and commerce sales back into their accounting software, and generate lending metrics for credit decisioning. The APIs split into raw data reads (Accounting, Banking, Commerce), writeback and sync flows (Bank Feeds, Sync for Commerce, Sync for Expenses), and derived metrics (Assess).

Does one Codat credential work across all of these APIs?

Yes. Every Codat API uses the same API key passed as a Basic Authorization header, so a single credential covers accounting, banking, commerce, the sync products, and Assess. You store it once and use it against any API in the portfolio.

How do the read APIs differ from the sync and feed APIs?

The Accounting, Banking, and Commerce APIs read normalised data out of a customer's systems, and the Accounting API can also write to the ledger. Bank Feeds, Sync for Commerce, and Sync for Expenses are purpose-built writeback flows that push bank transactions, commerce sales, and expenses into accounting software with the right mapping and lifecycle controls.

When should I use Assess instead of the raw data APIs?

BOOK A DEMO

Start Connecting APIs to Your AI Agents

Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.

Book a Demo

For Agents

APIs7 in catalogue

Endpoints254 indexed

AuthAPI key — 1 credential for all 7 APIs

ProvenanceOfficial OpenAPI specs

An agent can read normalised accounting, banking, and commerce data from a customer's linked platforms, push invoices, bills, bank feeds, expenses, and commerce sales back into their accounting software, and generate enhanced financial reports and lending metrics for credit decisioning. All of this works through one Codat credential across QuickBooks, Xero, Sage, Shopify, Square, Stripe, and other supported systems.

Codat normalises accounting, banking, and commerce data behind one schema so a single integration maps to 20+ underlying platforms, covering both reading data out of a customer's systems and writing it back in. Its APIs split cleanly into raw data reads, write-and-sync flows, and pre-computed lending metrics, letting a product pick exactly the layer it needs without building or maintaining connectors per platform.

Use for: Reading and writing normalised accounting, banking, and commerce data from a customer's linked financial platforms, and deriving lending metrics from it, through one unified integration across QuickBooks, Xero, Sage, Shopify, Square, and Stripe.

Not supported: payment processing, payment initiation, direct bank aggregation onboarding, real-time transaction streaming, consumer banking data

Credentials: All Codat APIs use the same authentication model: a single Codat API key passed in the Authorization header as Basic base64-encoded credentials, so one credential covers every API in the portfolio.

Which Codat API should I use?

I want to...	Use	Why
Read invoices, bills, journal entries, and reports from a customer's accounting ledger	Accounting API	Full read and write access to normalised accounting data across QuickBooks, Xero, Sage, and 17 other platforms.
Get ready-made lending metrics like enhanced P&L, MRR, and data integrity scores	Assess API	Derives underwriting metrics from already-linked accounting and commerce data instead of returning raw records.
Read a customer's bank accounts, balances, and categorised transactions	Banking API	Returns cleaned bank data from directly linked bank or open-banking sources for cash flow analysis.
Push bank transactions into accounting software as a native bank feed	Bank Feeds	Delivers transactions as a branded bank feed rather than reading data out of the ledger.
Read a merchant's orders, payments, products, and disputes from a commerce platform	Commerce API	Read-only normalised commerce data from Shopify, Square, Stripe, Amazon, and eBay in one schema.
Sync a merchant's commerce sales, fees, and refunds into their accounting software	Sync for Commerce	Manages the configured commerce-to-accounting sync flow with branding and lifecycle controls.

Install Jentic One Beta

Connect the Codat APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Codat APIs, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcodat.io" | sh

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

Once connected, ask your agent something like: “read and write a customer's accounting, banking, and commerce data”.

What AI Agents Can Do with Codat

Each workflow spans multiple Codat APIs. Jentic routes each operation to the right API automatically.

End-to-end SMB lending underwriting

A lender pulls raw ledger data with the Accounting API, cash flow history with the Banking API, and feeds them into the Assess API to produce enhanced profit and loss, cash flow, and data integrity scores. One Codat credential covers all three so a credit model can score a borrower without asking for document uploads.

Example prompt:

For company {companyId}, fetch the last 12 months of profit and loss from the Accounting API, pull categorised bank transactions from the Banking API, then retrieve the enhanced cash flow and data integrity summary from the Assess API and flag any month below 80 percent integrity.

APIs used

Accounting API + Banking API + Assess API

Commerce revenue diligence for revenue-based finance

A capital provider reads a merchant's orders, payments, and disputes with the Commerce API and derives cohort metrics like MRR, retention, and lifetime value with the Assess API. Both run off the same Codat connection so an underwriter can evaluate revenue quality across Shopify, Square, and Stripe from one integration.

Example prompt:

For company {companyId} connection {connectionId}, list the last 12 months of commerce orders and payments from the Commerce API, then fetch MRR, customer retention, and lifetime value from the Assess API and summarise revenue quality.

APIs used

Commerce API + Assess API

Full commerce-to-accounting reconciliation

A finance platform reads normalised orders and payments with the Commerce API and writes each day's sales, fees, and refunds into the accounting ledger with the Sync for Commerce API. The same credential reads the source data and configures the sync, so a merchant sees reconciled figures without manual exports.

Example prompt:

For company {companyId}, list commerce payments from the Commerce API grouped by order, then trigger a Sync for Commerce run and monitor it until it returns a final status.

APIs used

Commerce API + Sync for Commerce

Spend management writeback across feeds and expenses

A spend management platform posts raw bank-feed transactions with the Bank Feeds API and writes GL-coded expense entries with the Sync for Expenses API, both into the customer's accounting software. One Codat credential drives both writeback paths so finance teams get reconciled entries without CSV imports.

Example prompt:

For company {companyId}, post a batch of card transactions through the Bank Feeds API, trigger a Sync for Expenses run, then confirm both syncs reached a successful status.

APIs used

Bank Feeds + Sync for Expenses API

Codat APIs for AI Agents

Codat API Catalog

Finance5

E Commerce2

Why Jentic?

FAQs

Start Connecting APIs to Your AI Agents

Which Codat API should I use?

Connect the Codat APIs to your agent

What AI Agents Can Do with Codat

If you need a different Finance vendor