Codat APIs

7 APIs254 Endpoints2 Categories

API Catalog(5 of 7)

Accounting API

Codat's Accounting API provides a unified interface for reading and writing accounting data across 20+ accounting platforms including QuickBooks, Xero, Sage, NetSuite, and FreeAgent. It standardises invoices, bills, journal entries, customers, suppliers, payments, and financial reports so a single integration maps to all supported systems. The API supports both pull operations (read normalised data from a linked company) and push operations (create or update records back into the source ledger). It is designed for fintech applications, lending platforms, and B2B SaaS products that need accounting data from their customers' books.

135 endpoints

Assess API

Codat's Assess API turns raw accounting and commerce data into ready-made financial metrics and reports purpose-built for lending, underwriting, and risk decisioning. It produces enhanced profit and loss, balance sheet, and cash flow reports along with commerce metrics such as revenue, refunds, customer retention, and lifetime value derived from a borrower's linked accounting and commerce platforms. The API also returns data integrity scores so credit teams know how trustworthy the underlying figures are. It is used by SMB lenders, capital providers, and embedded finance platforms.

22 endpoints

Bank Feeds

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.

32 endpoints

Banking API

Codat's Banking API surfaces bank account, balance, transaction, and transaction-category data from a customer's directly-linked bank or open-banking provider. It is purpose-built for lenders, finance platforms, and underwriters that need cleaned bank transaction history alongside accounting data. Endpoints return account metadata, current balances, and categorised transactions so credit teams can verify cash flow and detect risk signals without parsing raw open-banking output.

8 endpoints

Sync for Expenses API

Codat's Sync for Expenses API lets corporate card and spend management platforms write expense transactions into a customer's accounting software with the right account mapping, tax rate, and tracking category applied. It manages partner-expense connections, mapping options, sync triggers, and per-transaction status so the platform can show finance teams exactly which expenses reached the ledger and which need attention. It is used by card issuers, expense apps, and travel-and-expense platforms that want one accounting integration covering QuickBooks, Xero, and Sage.

14 endpoints

Connect Your Agent

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.