Overview

Secure and efficient access to both API and file data

API.1 consists of both the API, our authentication and on-boarding processes and a file upload and parsing service called FILE.1. The combination provides a uniquely efficient and at the same time secure way to connect your customers systems and data to you.

Long and in-depth experience

Over several years we built a network of SAAS solutions and provided numerous integrations to both enterprise and business customers. Nets, Kivra and Björn Lundén to mention a few. With the API.1 solution we add an API that is easy for you to use and provide access to the most relevant systems and files.

You only need to decide what to do with the data

Mapping, system and regulations know-how, maintenance, authentication and connections are handled by us. You only need to connect once to API.1 and decide what to do with the data. Every new system or file format that we add, is immediately made available to you, which makes it easy to expand on different markets or enhance and improve your offerings toward your business customers.

The most common use cases are factoring, credit assessments and automation of e.g. accounting

The most common use cases are bank or finance companies that need access to invoice data, to be able to provide factoring or similar invoice related services as a start and add data for better credit assessments and services going forward. We also collaborate with payment solution providers to help them automate accounting of payouts and add accounting data to for example their assessments. We are adding both more systems, file types, data entities and regions going forward, making it easy for you to make use of API.1 to empower your services and grow.

Getting Started

The process is simple

1. Sign up with Zwapgrid connect to API.1
2. Invite your customer to consent
3. Your customer connects their ERP system and/or uploads their files.
4. You get access to their data in a unified way

The getting started process consists of the following steps

You will now have access to, e.g. invoices from your customers as long as they use a system in our network.

Connecting to our API

This is our comprehensive documentation for API.1, allowing your developers to interact with the API and fully understand how it works, before having to write a single line of code.

Generally, our API uses these principles

1. Connect to API.1 using Auth0 2.0, hosted in the cloud.
2. A suite of RESTful APIs that let you create and manage your customers within API.1.
3. A suite of vendor-agnostic RESTful APIs to let you access your customer data.

To connect, there are a few APIs to be aware of and their purposes

API.1 consists of three two parts:

1. The Client API where we handle and authenticate our Client
2. The (End) Customer API where end customers can be invited to give data sharing consent.

The Onboarding Journey

Design your own onboarding experience. You decide how to invite your customer and what the journey should be to prime the customer into sharing their data. Zwapgrid requires a very simple sign-up. The customer is presented with their ERP system to sign in with their ERP system credentials. The customer's ERP system will present them a consent page to share their data. Customer agrees to share their ERP data and that's it! It's a three screen process. You can decide the after journey, thank your customer or redirect them elsewhere. Easy, convenient and customizable.

Fetching Data

To fetch data, you will need to have a customer consent first. In this process, you have already created a connection to API.1 and have invited your customer. Your customer has successfully completed the onboarding journey.

Once the end customer has successfully connected their ERP system to our API, we create a consent ID for that customer. Call the Client API to retrieve your customer consent ID. The consent ID is used in the next process to fetch the data.

Fetching Data with API.1 is simple!

With the customer consent ID, call the API of interest. You will receive a list of entities from that API with unique IDs for each entity. Fetch a specific entity by using the entity ID. Now you have that entity to use in your products.

Here we have exemplified the process using the Accounting API and the entity: Invoices. Go to our tab: Systems in the grid, to see all the entities we offer with API.1.