search
Developer GuideAPI GuideChangelogDeprecation ScheduleStatus

Overview

Zwapgrid makes getting your business customers' data simple and secure. Ditch the endless integrations. Just connect once, invite your customers, and seamlessly access the data you need.

Zwapgrid is a platform for accessing your customers’ accounting data through one integration.

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 customers connect 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 customers to connect their accounting system.

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

  • File.1 to upload and extract data from files (for example invoices).

  • Client Portal to manage environments and API keys.

hashtag
End-to-end flow

  1. Create a consent in the Consent API.

  2. Invite your customer to the onboarding flow.

  3. The customer connects their accounting system (or uploads files).

  4. Poll the Accounting API to retrieve the 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.

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?