One integration.
Every ledger your
customers run on.
Fintechs, banks and vertical SaaS build once against the Accounting API — then read and write invoices, bills, payments and journal entries across 48 accounting systems. Your customer authorizes once through Vault: no credentials on your servers, and no copy of their ledger anywhere.
QuickBooks
NetSuite
Xero
Sage Intacct
Exact Online
FreshBooks+42 moreThe same platform covers HRIS, CRM, ATS and more — 200+ connectors in total. These tours use accounting because it's where most customers start.
Start with the overview. Then go as deep as you like.
The whole idea in one pass: one integration, every connector. The lifecycle from a customer's login to an AI agent, the unified APIs per category, and what Apideck already handles that you'd otherwise own.
- Inside
- Three ideas do all the work
- The path: connect → call → normalize → automate
- One schema per category
- The plumbing we already built
- 200+ connectors
How Apideck represents your customers: consumer IDs, when one company needs more than one consumer, how consumers get created, and the three headers that route every API call.
- Inside
- What a consumer is
- One consumer vs many
- Creating a consumer
- The consumer dashboard
- The headers on every call
The embeddable component your customers use to connect their own accounts — embedded or hosted — plus the APIs and webhooks around it, and what happens when a resource isn't consented.
- Inside
- What Vault is
- Embedded Vault
- Hosted Vault
- Vault APIs and webhooks
- When a resource isn't consented
What Apideck stores and what it deliberately doesn't. Why the downstream system stays the source of truth, and what one normalized model looks like across two very different ledgers.
- Inside
- The source of truth
- What Apideck stores
- One model, every connector
- If you need a cache
Every call is kept as a linked pair: the unified request you made, and the raw request Apideck made downstream. The fastest way to see why a connector rejected a write.
- Inside
- The linked pair
- The parent call
- The child call
- Reading a failure
The same unified layer is an MCP server. Point Claude or Cursor at it and an agent reads and writes across every connector — four meta-tools keep its context window small enough to be practical.
- Inside
- One server, every unified API
- Four meta-tools, not four hundred
- The discovery sequence
- Connecting your own agent
- Scoping what it can reach
Your customers already live in other tools. And no two work the same way.
Your product needs their data out of QuickBooks, Xero, NetSuite, Salesforce and a few hundred more. Every one of them is a different protocol, a different auth model, and a different set of edge cases.
QuickBooksREST / JSONOAuth 2.0NetSuiteSOAP / XMLToken-basedSage IntacctXML gatewaySession-based
SalesforceREST / JSONOAuth 2.0Months of engineering for every app you add — and it never stops.
One API instead of hundreds. One line changes.
Integrate Apideck once, then read and write to every app in a category. Only the service id differs between QuickBooks, Xero and NetSuite — same call, same response shape.
the highlighted line is the only difference between ledgers
Customers connect their own accounts through Vault. Credentials, tokens and refresh live with Apideck — never on your servers.
You write the product. We handle the plumbing.
- Your business logic — using our SDKs for TypeScript, Python, PHP and more.
- Vault, dropped into your app — so customers connect their own accounts.
- Authentication, token storage and refresh
- Connection management and the end-user experience
- One normalized data model across every connector
- Retries, error handling and request logs
- 200+ connectors, kept current as their APIs change
- Custom field mapping, per consumer
The idea is simple: you ship features, not integrations. See the whole platform