Apideck CLI: Query 200+ SaaS APIs from your terminal. No SDK needed. Read more

Apideck Documentation Page

Intuit Bank Feeds – Connection Guide

Service ID: intuit-bank-feeds

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

How to connect to Intuit Bank Feeds

The Intuit Bank Feeds connector stores your bank-feed accounts and statements with Apideck's FDX data provider, where QuickBooks Online picks them up. Connecting in Vault needs no credentials: Apideck sets up everything the connection needs when you enable it. The QuickBooks Online user then links the feed from inside QuickBooks.

Prerequisites

  • Access to the application's Vault, or an application that creates the connection for you through the Vault API.
  • No QuickBooks app, API key, or QuickBooks OAuth connection is needed. Connecting the QuickBooks connector does nothing for this one.
  • For the QuickBooks side: before step 5 can work, the application owner must have registered its bank brand with Intuit (Intuit FDP registration) so the brand is listed in QuickBooks Online, and must have set up the application's customer login page (the Customer login settings in the Apideck Dashboard, explained in the Configuration Guide). The QuickBooks Online user who links the feed must be able to sign in on that customer login page. The client, not their accountant, must do this.

Steps

Connect in Vault

  1. Enable the connection. Open Intuit Bank Feeds in Vault and enable it, or have your application create the connection through the Vault API. There is no sign-in screen for you in Vault and nothing to paste.
  2. Let Apideck provision it. Enabling the connection prompts Apideck to create a dedicated data space for it with Apideck's FDX data provider and to store the access credentials for that space on the connection. You never see or handle these credentials.
  3. Wait for the connection to become ready. Apideck checks the connection's readiness. While provisioning finishes, the connection can stay in the added state (shown as Unauthorized in Vault) for a short time; this does not mean the connection failed, so do not delete it. Once the readiness check passes, the connection is callable.
  4. Start sending data. Your application can now create bank-feed accounts and statements on this connection.
  1. Connect the account in QuickBooks Online. The QuickBooks Online user goes to All apps > Accounting > Bank transactions and selects Connect account (or Link account if an account is already connected). They search for the bank (listed in QuickBooks through the application owner's Intuit FDP registration), select Continue, and sign in on the customer login page hosted by the application that offers the bank feed, at the Login URL the application owner configured. After completing any security steps and the consent screen, they select the accounts to connect, choose a start date, and select Connect, then Done. Intuit's connect a bank or credit card account article walks through the QuickBooks screens.

Notes

  • No redirect URL. The Vault connection has no OAuth flow, so there is no redirect or callback URL to configure.
  • Disconnecting deletes the stored data. Deleting the connection removes its data space along with every account and statement stored in it. Only delete the connection when you no longer need that data.

Troubleshooting

  • The connection stays in added (shown as Unauthorized in Vault). Provisioning can take a moment to complete, and the connection becomes callable as soon as the readiness check passes. If it stays in added (Unauthorized in Vault), contact Apideck Support with the connection ID rather than deleting it, because deleting the connection also deletes its stored data.
  • Requests fail with an invalid-credentials error (401). The credentials stored on the connection were not accepted by its data space. Contact Apideck Support with the connection ID before deleting anything, because deleting the connection also deletes its stored data.
  • Requests fail because the data space cannot be found (404). The connection's data space no longer exists while the connection itself still does. Delete the connection and enable it again to provision a new data space; nothing more is lost, because the old data space is already gone.
  • The bank is not listed in QuickBooks Online, or the login page does not load. Contact the application owner whose application offers the bank feed: getting the bank brand listed in QuickBooks (its Intuit FDP registration) and hosting the customer login page are on their side, not something the QuickBooks user can change.