FAQ

Frequently asked questions about Apideck

Everything teams ask before shipping with Apideck: what the unified API platform does, how OAuth works, what we charge, how we handle security, which use cases we support, and where we fit if you have already started building integrations in-house.

Last updated

What exactly is Apideck, and how does it work?

Apideck provides a unified API that connects your product to 30+ accounting and ERP platforms, including QuickBooks, Xero, Sage, and NetSuite, through a single integration. You integrate once with Apideck and instantly offer your customers the ability to connect their accounting platform of choice. We handle all the heavy lifting: authentication, data normalization, error handling, logging, and maintenance.

What use cases does Apideck's Accounting API support?

Apideck's unified accounting API supports every major accounting and ERP use case, including:


All APIs are standardized, making it easy to deploy multiple use cases without having to rewrite logic.

See all use cases →

How long does it take to integrate Apideck?

You can go live in a matter of days or weeks (depending on the use case). With one common data model, prebuilt connectors, an embedded white-label auth UI, and centralized error logging, your team avoids months of API research, custom integration logic, and ongoing maintenance.

How do you handle OAuth, token refresh, and user connections?

We provide an embedded white-label UI that handles:

  • OAuth authorization flows
  • Token refresh and rotation
  • Connection status tracking
  • Secure token storage

This means your team doesn't have to worry about credential handling or connection state logic—we've already built it.

Can we customize the data we pull or send?

Yes. Apideck supports:

  • Custom field mapping to your internal schema
  • Data scoping to limit access to only the fields you need
  • Passthrough raw data access, so nothing is lost from the source platform

You get both a normalized structure and access to the raw API response when needed.

Learn more about field mapping →

How does Apideck handle logging and debugging?

Every API request, response, and webhook is logged. You get:

  • A centralized dashboard for cross-connector monitoring
  • Visibility into integration health per customer
  • Fast issue diagnosis without digging through external platform logs

This reduces support time, makes integration bugs easier to resolve, and improves reliability for your customers.

Is Apideck secure? Do you store our data?

Apideck does not persist third-party data on our infrastructure. All API calls are processed in real time and passed directly from the source to your app, avoiding caching delays, reducing latency, and minimizing data breach risk. We follow best-in-class security practices and are SOC 2 Type II certified and GDPR-compliant.

How is Apideck priced?

Apideck offers flexible pricing models to fit your business needs: Consumer-based pricing (default): Pay per active consumer, which is each customer connected through Apideck whose end user actively uses an integrated platform that month. Best for predictable billing and most SaaS integration patterns. API call-based pricing (opt-in): Pay based on actual API usage. Available on request for teams with high connection counts and variable customer activity. We intentionally avoid "per-connector" pricing, which penalizes growth and limits flexibility. Compare pricing models →

How is your unified API different from building direct integrations ourselves?

Building and maintaining direct integrations with each accounting platform requires constant API research, one-off auth flows, inconsistent data models, and ongoing maintenance every time something changes.

Apideck solves this by offering:

  • One standardized data model
  • A white-labeled auth flow
  • Centralized logging and monitoring
  • Ongoing connector maintenance and updates

Instead of spending months building brittle integrations, your team ships in days, without sacrificing control or visibility.

Can we use Apideck in staging or sandbox environments before going live?

Yes. All Apideck plans come with sandbox support so you can safely test integrations in staging environments before rolling them out to production. You get access to test credentials and simulated data responses to validate flows end-to-end.

Can we test the product before committing to a paid plan?

Absolutely. We offer a 30-day free trial with full access to Apideck's functionality—so your team can test everything from connector behavior and auth flows to logging and performance before committing to a paid plan.

What happens if a third-party platform's API goes down or changes?

Apideck actively monitors all third-party connectors for API outages, changes, and deprecations, so you don't have to. We proactively adapt to API updates and handle breaking changes—saving your team from constant doc-watching and urgent patching. It's one of the key benefits of choosing a platform like ours over building and maintaining direct integrations in-house.

Still have a question?

Talk to a unified API specialist or start a free trial and try Apideck against the platforms your customers actually use.