---
title: "Apideck joins FDX, the body behind the FDX API"
description: "Apideck has joined FDX, the standards body behind the FDX API. What it means for accounting and ERP integrations that move bank data."
author: "Bernard Willems"
published: "2026-08-17T09:00+02:00"
updated: "2026-08-14T12:09:17.295Z"
url: "https://www.apideck.com/blog/apideck-joins-fdx-financial-data-exchange"
tags: ["Company news"]
---

# Apideck joins FDX, the body behind the FDX API

Apideck has joined the [Financial Data Exchange](https://financialdataexchange.org/about-fdx/) (FDX). FDX maintains the FDX API, the technical standard for user-permissioned financial data sharing in the United States and Canada, and it is what the North American market is standardising on.

FDX has [around 200 member organisations](https://financialdataexchange.org/): banks, data aggregators, fintechs, payment networks and consumer groups. The standard is royalty-free, and by [the Open Banking Tracker's 2025 count](https://www.openbankingtracker.com/standards/fdx) it sat behind more than 114 million customer connections and roughly 75% of the US market. 

The CFPB named FDX the first standard-setting body under Section 1033 in January 2025. That rule is now enjoined and being rewritten, and [the compliance deadlines have not held](https://www.openbankingtracker.com/guides/section-1033-status), but the market has kept converging on FDX regardless. That is the version of the standard we want a seat at: the one the industry is building to while the regulation is still unsettled.

## Why the FDX API matters for accounting and ERP integrations

The names on the FDX member list are not only banks. [Intuit and Xero have both been members](https://financialdataexchange.org/fdx-feed/financial-data-exchange-adds-11-new-members-makes-api-publicly-available/) since the body's early years, Intuit from a board seat. The accounting platforms our customers integrate with sit in the same standards body as the banks whose data has to reach them.

That overlap is the reason we joined. Apideck builds integration infrastructure for B2B software, and the deepest part of our catalogue is accounting and ERP: 45+ connectors, including QuickBooks and NetSuite. For a growing number of the companies building on them, accounting data alone is not the job. They are [moving bank and card transactions into an accounting platform](https://www.apideck.com/blog/quickbooks-bank-feed-integration), or pulling ledger data out to [reconcile it against statements held at several banks](https://www.apideck.com/blog/treasury-management-systems-multi-bank-connectivity-integrations). 

Apideck's job starts where that bank data lands. Our customers need those records to arrive correctly in the accounting and ERP systems their own customers run, and [the cost of getting it wrong](https://www.apideck.com/blog/financial-api-integration) is mostly paid in engineering time nobody budgeted for. Membership is how we keep our end of that pipe aligned with the standard the other end is being built to.

In practice it means a place in the working groups where the FDX API is drafted, alongside the banks and the accounting platforms our customers depend on, and sight of where the standard is heading well before it publishes. The corporate and treasury side of the standard is younger than the consumer side, and that is where we are spending our time.

If you are working on bank feeds inside an accounting or ERP integration, [our guide to bank feeds API integration](https://www.apideck.com/blog/bank-feeds-api-integration) is a good place to start.