search
Developer GuideAPI GuideChangelogDeprecation ScheduleStatus

Overview

Zwapgrid makes getting Your Customer's data simple and secure. Ditch the endless integrations. Just connect once, invite Your Customer, and seamlessly access the data you need.

Zwapgrid is a platform for accessing Your Customer's accounting data through one integration.

New to Zwapgrid? Start here: (1) Overview (this page), (2) Terminology, (3) How the platform works, (4) Get Started overview, (5) Onboard Your Customer, (6) Access Your Customer Data.

It combines a unified API, a consent-driven onboarding flow, and a file ingestion service. You ship your product. We handle the system-by-system complexity behind the scenes.

hashtag
What is API.1?

API.1 is the single connection point for reading data from many accounting systems.

You integrate once. Your Customer connects their system during onboarding. You then fetch data in a consistent format.

hashtag
Why Zwapgrid + API.1 works well

  • One integration, many systems. Avoid building and maintaining one-off connectors.

  • Unified schema. API.1 normalizes system differences into one data model.

  • Less operational burden. We handle auth flows, token refresh, and connector upkeep.

  • Customer-friendly onboarding. Customers grant access in a guided, branded flow.

  • API-first with a file fallback. If there is no API, use File.1 for uploads and parsing.

  • Built for controlled access. Data access is consent-based and auditable by design.

  • Security-focused defaults. See API Security for specifics.

hashtag
What you get (building blocks)

  • Consent API to create and manage customer consent.

  • Onboarding Flow for Your Customer to connect their Accounting System.

  • Accounting API to fetch normalized data after consent is granted.

  • File.1 – Use when there is no API for the system or you need to ingest files (e.g. PDF invoices). See File.1 overview.

  • Proxy.1 – Use when you need to call the underlying accounting system's API directly through Zwapgrid (same auth, normalized base URL). See Proxy.1 overview.

  • Client Portal to manage environments and API keys.

End-to-end flow: consent, onboarding, and data access.

hashtag
End-to-end flow

  1. Create a consent in the Consent API.

  2. Invite Your Customer to the Onboarding Flow.

  3. Your Customer connects their accounting system (or uploads files).

  4. Poll the Accounting API to retrieve Your Customer’s data.

For the practical steps, start here:

hashtag
Technical model (at a glance)

API.1 is split into two APIs:

  • Consent API for consent lifecycle and status.

  • Accounting API for reading data from connected systems.

Use the Consent API to create consents and generate One-Time Codes; use the Accounting API (with that Consent ID in the path) to read invoices, company information, and other accounting data.

Operationally, API.1 is designed for polling-based data retrieval. It also supports traceability via correlation IDs.

Next reads:

NextSystems in the grid

Last updated

Was this helpful?