Source connector

Codat connector

Codat integration for databases, warehouses and BI tools

Unified API for accounting and banking data. Datrise captures Codat entities such as companies, accounts, invoices, bills, journal entries and payments, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Codat Platform API authenticates with API key, HTTP Basic, incremental runs key on modifiedDate, and Codat caps calls at 1,000 x (1 + number of Active Connected Companies) requests per day, 10 concurrent requests per connected company, and a hard 1,000 requests per minute per IP; quotas reset at 00:00 UTC.

Of the 6 objects, 4 sync as upserts keyed on the primary key and 2 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `codat_companies`) with a schema derived from the Codat API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Codat pipeline page, and join the waitlist to get the Codat connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Codat data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
companies	codat_companies	Upsert by primary key, incremental on updated-at
accounts	codat_accounts	Upsert by primary key, incremental on updated-at
invoices	codat_invoices	Append-only, incremental by timestamp
bills	codat_bills	Upsert by primary key, incremental on updated-at
journal entries	codat_journal_entries	Upsert by primary key, incremental on updated-at
payments	codat_payments	Append-only, incremental by timestamp

Codat API: setup facts for the connector

Verified against the vendor documentation on 2026-09-03. Unknown values are left blank rather than guessed.

API	Codat Platform API
Authentication	API key, HTTP Basic — A Base64-encoded API key sent as `Authorization: Basic {key}`; an account may hold at most 10 API keys at a time.
Pagination	page — `page` (default 1) and `pageSize` (default 100, maximum 5000); responses carry `results`, `totalResults` and a `_links` object with `next` and `previous`.
Rate limit	1,000 x (1 + number of Active Connected Companies) requests per day, 10 concurrent requests per connected company, and a hard 1,000 requests per minute per IP; quotas reset at 00:00 UTC
Incremental cursor	modifiedDate — `modifiedDate` is when the record changed in Codat's own store; `sourceModifiedDate` is when it changed in the underlying accounting platform and is not populated by every platform.
Webhooks	Yes — Codat webhook service (event types subscribed via the Portal or API, with retries and event replay)
Bulk export	No
Deletes detectable	Not published

Official API reference

What bites when replicating Codat

The daily quota scales with Active Connected Companies (1,000 x (1 + ACCs)), so a sandbox or low-volume account has a far smaller budget than production and hits 429 during a first backfill.
`pageSize` can be raised to 5,000 but Codat explicitly recommends the default of 100 for response times; deep paging at the maximum is where timeouts appear.
`sourceModifiedDate` is not populated by every accounting platform, so an incremental sync keyed on it silently misses records — `modifiedDate` is the only universally present cursor.
`totalResults` counts rows after the `query` filter is applied, not the full data set, so it cannot be used to detect that a filter dropped records.

Compare this against every other documented API

Popular destinations for Codat

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Codat connector FAQ

What Codat data does the connector extract?: 6 objects: companies, accounts, invoices, bills, journal entries and payments. Each lands in its own table with types preserved; history-style objects (2: invoices and payments) load as append-only streams.
Is the Codat integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Codat data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Codat → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Codat pipeline with guided onboarding

Join the waitlist to get priority access for Codat integrations with guided setup, schema-aware mapping, and production-grade incremental sync.