YBuilt for your teamSign up Schedule a demo

01/06

The Apideck platform

One integration.
Every SaaS your
customers use.

Build once against a unified API — Accounting, HRIS, CRM and more — and ship integrations to 200+ connectors. Apideck handles the auth, the data models and the edge cases.

Explore the demos Read the docs

The idea

Three ideas do all the work.

Integrations get hard because every vendor is different. Apideck collapses that difference into three primitives — then everything downstream is the same call, over and over.

One model per category

Accounting, HRIS, CRM — each is a single normalized schema. Learn the Invoice once; it maps to every ERP underneath.

One connection, managed

Apideck Vault stores, rotates and refreshes every token. Credentials never reach your servers.

One call, every connector

Change a serviceId, not your code. Request and response shapes stay identical across 200+ integrations.

The path

From a customer's login to an AI agent — four steps.

Scroll through the lifecycle. The panel follows along — watch the one line that changes when the connector does, and everything that doesn't.

01Connect

Apideck Vault

Your customer authorizes once.

Drop in the embedded Vault flow. They pick their tool and sign in on the provider's own screen — OAuth, an API key, whatever it needs. Apideck stores and refreshes the tokens. Secrets never touch your servers.

CustomerAikido— white-label Vault auth · 3,000 customers live

Connect
Call
Normalize
Automate
// 1 · CONNECT — your customer authorizes their tool, once
const session = await apideck.vault.sessionsCreate({
  consumerId: "customer_42",
});
// → open session.data.session_uri in the Vault modal
 
// 2 · CALL — one unified endpoint per category
const { data: invoices } = await apideck.accounting.invoicesAll({
  serviceId: "quickbooks",
  consumerId: "customer_42",
});
 
// 3 · NORMALIZE — swap the connector, not your code
//   → the SAME Invoice[] shape, every connector
 
// 4 · AUTOMATE — the same platform is an MCP server
// agent → execute_tool("accounting-invoices-all")
// …across 200+ connectors, on demand — no glue code
token stored · auto-refreshed

02Call

Unified API

Build against one API.

One unified endpoint per category — Accounting, HRIS, CRM and more. One request shape, one auth model, whether QuickBooks or NetSuite is behind it.

CustomerRound Treasury— 160 hours saved integrating NetSuite

Connect
Call
Normalize
Automate
// 1 · CONNECT — your customer authorizes their tool, once
const session = await apideck.vault.sessionsCreate({
  consumerId: "customer_42",
});
// → open session.data.session_uri in the Vault modal
 
// 2 · CALL — one unified endpoint per category
const { data: invoices } = await apideck.accounting.invoicesAll({
  serviceId: "quickbooks",
  consumerId: "customer_42",
});
 
// 3 · NORMALIZE — swap the connector, not your code
//   → the SAME Invoice[] shape, every connector
 
// 4 · AUTOMATE — the same platform is an MCP server
// agent → execute_tool("accounting-invoices-all")
// …across 200+ connectors, on demand — no glue code
200 · 50 invoices returned

03Normalize

One schema, every connector

Swap the connector. Your code doesn't.

Change a single serviceId and the response comes back in the exact same normalized shape — no per-vendor branching, no field remapping. The one field that changes is highlighted; nothing else does.

CustomerDerive— one integration, every ERP

Connect

Call

Normalize

Automate

// 1 · CONNECT — your customer authorizes their tool, once

const session = await apideck.vault.sessionsCreate({

consumerId: "customer_42",

});

// → open session.data.session_uri in the Vault modal

// 2 · CALL — one unified endpoint per category

const { data: invoices } = await apideck.accounting.invoicesAll({

serviceId: "quickbooks",

consumerId: "customer_42",

});

// 3 · NORMALIZE — swap the connector, not your code

// → the SAME Invoice[] shape, every connector

// 4 · AUTOMATE — the same platform is an MCP server

// agent → execute_tool("accounting-invoices-all")

// …across 200+ connectors, on demand — no glue code

Invoice[] — identical shape quickbooks logo

Invoice[]

04Automate

MCP server

Hand the platform to an agent.

The same unified layer is an MCP server. An AI agent discovers tools and runs execute_tool across every connector — four meta-tools keep its context window tiny.

CustomerOcta— AI finance automation · weeks of dev saved

See the MCP server See it in the demos

Connect
Call
Normalize
Automate
// 1 · CONNECT — your customer authorizes their tool, once
const session = await apideck.vault.sessionsCreate({
  consumerId: "customer_42",
});
// → open session.data.session_uri in the Vault modal
 
// 2 · CALL — one unified endpoint per category
const { data: invoices } = await apideck.accounting.invoicesAll({
  serviceId: "quickbooks",
  consumerId: "customer_42",
});
 
// 3 · NORMALIZE — swap the connector, not your code
//   → the SAME Invoice[] shape, every connector
 
// 4 · AUTOMATE — the same platform is an MCP server
// agent → execute_tool("accounting-invoices-all")
// …across 200+ connectors, on demand — no glue code
agent · execute_tool ✓

Connect
Call
Normalize
Automate
// 1 · CONNECT — your customer authorizes their tool, once
const session = await apideck.vault.sessionsCreate({
  consumerId: "customer_42",
});
// → open session.data.session_uri in the Vault modal
 
// 2 · CALL — one unified endpoint per category
const { data: invoices } = await apideck.accounting.invoicesAll({
  serviceId: "quickbooks",
  consumerId: "customer_42",
});
 
// 3 · NORMALIZE — swap the connector, not your code
//   → the SAME Invoice[] shape, every connector
 
// 4 · AUTOMATE — the same platform is an MCP server
// agent → execute_tool("accounting-invoices-all")
// …across 200+ connectors, on demand — no glue code
token stored · auto-refreshed

200+ connectors340+ toolsone integration

Unified APIs

One schema per category. Every connector underneath.

Invoices, bills and the ledger — normalized across every ERP.

Normalized models

InvoicesBillsPaymentsLedger AccountsJournal EntriesBalance Sheet

45+connectors · one integration

quickbooks

xero

netsuite

sage intacct

freshbooks

exact online

Interactive

The plumbing? We already built it.

Everything you'd own by building the integration layer yourself maps to a piece of Apideck that already handles it. Pick a concern to see how.

Handled by

Vault, managed OAuth

Vault stores and refreshes OAuth tokens across every connector. Your users authorize once and Apideck keeps each connection alive — you never build or babysit per-provider auth.

vault · connections

QuickBooks Online token fresh

HubSpot token fresh

BambooHRAuthorize

refreshed automatically · secrets never reach your servers

Coverage