Accounting API

Ledger Accounts

Tax Rates

Company Info

Invoices

Customers

Bills

Suppliers

Invoice Items

Payments

Credit Notes

Journals

Journal Entries

Subsidiaries

BalanceSheet

ProfitAndLoss

Purchase Orders

Locations

Departments

Attachments

Tracking Categories

Bill Payments

Expenses

Aged Creditors

Aged Debtors

Bank Feed Accounts

Bank Feed Statements

Quotes

Sales Orders

Bank Accounts

Projects

Refunds

Payment Methods

Sales Receipts

Goods Receipts

Companies

Employees

Expense Categories

Expense Reports

Bill Credit Notes

General Ledger Transactions

Intuit Bank Feeds delivers bank-feed accounts and statements into QuickBooks Online through Apideck's FDX data provider, fdx-connect.

connection

customer_login

Intuit Bank Feeds

Single environment: testing and production share one connection. End-to-end testing is expected to happen in Intuit's pre-production run during FDP implementation, so treat anything you write as production data that can reach QuickBooks Online.

Bank Feeds

The people or businesses that hold the source bank account. Optional; `plaid-exchange` requires at least one.

A person or business that holds the source bank account. Connectors that serve account contact data to a bank-feed consumer (`plaid-exchange`) require each holder to carry `first_name` and `last_name`, or `business_name` when the holder is a business.

Bank Feed Account Holder

Account Holders

Addresses of the account holders. Optional; `plaid-exchange` requires at least one.

edge-case

Addresses

The available balance of the source bank account (considering pending transactions and overdraft).

Available Balance

The current balance of the source bank account.

Current Balance

Bank Account Type

Country code according to ISO 3166-1 alpha-2.

Country Code

The date and time when the object was created.

Created at (timestamp)

Created by

Indicates the associated currency for an amount of money. Values correspond to [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217).

Currency

UNKNOWN_CURRENCY

medium

When custom mappings are configured on the resource, the result is included here.

Email addresses of the account holders. Optional; `plaid-exchange` requires at least one.

Emails

Feed Status

Phone numbers of the account holders. Optional; `plaid-exchange` requires at least one.

Phone Numbers

Source Account ID

Account Number

Routing Number

The target account's unique identifier in the accounting connector.

Target Account ID

Target Account Name

Account number of the destination bank account.

Target Account Number

The date and time when the object was last updated.

Updated at (timestamp)

Updated by

The ID of the bank feed account this statement belongs to.

Bank Feed Account ID

End Balance

Credit or Debit

End Date

Balance amount at the start of the period.

Start Balance

Start Date

The current status of the bank feed statement.

Statement Status

List of transactions in the bank feed statement.

Bank Feed Statement Transactions

`feed_status` reads back as `pending` for every account in this release — it does not yet reflect
whether QuickBooks has picked the feed up.


**No QuickBooks OAuth connection is required or used.** `intuit-bank-feeds` is a separate connector
with its own connection lifecycle, so a bank-feeds-only integration never authenticates to
QuickBooks: connecting `quickbooks` does nothing for this connector, and this connector needs
nothing from it.

A connection only becomes callable once it reports ready, so a newly created one can briefly stay
in the `added` state. Re-check it and retry rather than reading `added` as a failure.

Field handling is stricter than the unified contract: `null` is rejected rather than ignored, so
omit an optional field instead of sending `null` for it. `feed_status` is not returned on this
create response — read the account back to see it.

`account_holders`, `emails`, `addresses` and `phone_numbers` are optional here. Each list holds at
most 10 items. Only the fields the bank-feed provider stores are forwarded: an address keeps
`type`, `line1`–`line3`, `city`, `state`, `postal_code` and `country`, and `id` is dropped from
every item.


List responses carry statement metadata only — `transactions` is never included, however many
statements the page holds. Fetch a single statement by id to read its transactions.


A successful create does **not** mean QuickBooks has the statement. This connector is pull-based:
the statement is stored on the Apideck side and waits there for Intuit's scheduled pull. That is a
fundamental difference from `xero`, where a successful push means Xero already holds the data.
Because delivery happens later and out of band, `status` reads back as `pending` and does not
advance to `success` in this release; a `status` other than `pending` sent on write is rejected.

Statements are validated on the way in, and a violation is **rejected** — never silently dropped:

- At most 1000 entries in `transactions`.
- Every `source_transaction_id` must be unique, both within the statement and against transactions
  already submitted for the same bank feed.
- Transactions must be in chronological order: `posted_date` must be non-decreasing across the
  array.
- Posted transactions only — pending or authorization-hold transactions are not accepted.
- `description` is limited to 255 characters.
- Every timestamp needs an explicit timezone offset: `start_date`, `end_date` and each
  transaction's `posted_date` must end in `Z` or `±hh:mm`. A bare local datetime such as
  `2026-01-15T12:00:00` is rejected, even though the unified `date-time` format permits it.
- `null` is rejected rather than ignored. Omit an optional field instead of sending `null` for it.

A rejected statement comes back with every violation at once, each naming the rule it broke, so a
single round trip shows all of them.


`transactions` **is** returned here, unlike the list operation, which carries statement metadata
only. Fetching a statement by id is the only way to read its transactions.

`status` reads back as `pending`. See the create operation for why it does not advance to
`success` in this release.


Task	You (Customer)	Your Consumer	Apideck
Intuit FDP Registration (per Brand)	✓	—	FDX data provider to Intuit
Host Customer Login Page (Login URL + JWKS URL)	✓	—	Guide provided
Enable Connection	✓ (if created via Vault API)	✓ (if enabled in Vault)	Provisions tenant and ingest key
Write Accounts and Statements via Unified API	✓	—	Maintains connector
Serve Data to Intuit (FDX)	—	—	✓

Intuit Bank Feeds

At a Glance

Responsibility matrix

Environments

🚨Important to Know About Intuit Bank Feeds