> For the complete documentation index, see [llms.txt](https://docs.zwapgrid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zwapgrid.com/proxy.1/proxy.1.md).

# Overview

Proxy.1 enables you to utilise Zwapgrid-supported onboarding, and exposes the underlying APIs for supported systems so that you can interact directly without the need to set up and manage a deep integration with those systems. You can make use of API.1 in order to simplify how you connect to each supported API in a standard way, using Zwapgrid API keys.

## Proxy Base URL

For all systems, replace the original API URL with:

`https://apione.zwapgrid.com/accounting/api/v1/consents/<consent_id>/proxy`

## Supported Systems

Today, we support the following systems:

* **Spiris**
  * Replace: `https://eaccountingapi.vismaonline.com/v2` with the proxy base URL
  * API Documentation: <https://eaccountingapi.vismaonline.com/scalar/v2>
* **Microsoft Business Central**
  * REST API: Replace `https://api.businesscentral.dynamics.com/v2.0/<tenantid>/Production/api/v2.0/companies(<company-id>)` with the proxy base URL
    * API Documentation: <https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference/v2.0/>
  * OData API: Replace `https://api.businesscentral.dynamics.com/v2.0/<tenantid>/Production/ODataV4/Company('<company-name>')` with the proxy base URL
    * Use request header: `x-use-odata: true`
    * API Documentation: <https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/webservices/odata-web-services>
* **Fortnox**
  * Replace: `https://api.fortnox.se` with the proxy base URL
  * API Documentation: <https://api.fortnox.se/apidocs>
* **Bjorn Lunden**
  * Replace: `https://apigateway.blinfo.se/bla-api/v1/sp` with the proxy base URL
  * API Documentation: <https://developer.bjornlunden.se/api-documentation/>
* **Visma e-conomic**
  * REST API: Replace `https://restapi.e-conomic.com` with the proxy base URL
    * REST API Documentation: <https://restdocs.e-conomic.com/#tl-dr>
  * OpenAPI: Replace `https://apis.e-conomic.com` with the proxy base URL
    * Use request header: `x-use-openapi: true`
    * REST API Documentation: <https://apis.e-conomic.com/>
* **Tripletex**
  * Replace: `https://tripletex.no/v2` with the proxy base URL
  * API Documentation: <https://tripletex.no/v2-docs/>
* **Procountor**
  * Replace: `https://api.procountor.com/api` with the proxy base URL
  * API Documentation: <https://dev.procountor.com/api-reference/>
* **Visma Netvisor**
  * Replace: `https://isvapi.netvisor.fi` with the proxy base URL
  * API Documentation: <https://developer.visma.com/api/netvisor>
* **Billy**
  * Replace: `https://api.billysbilling.com/v2` with the proxy base URL
  * API Documentation: <https://www.billy.dk/api/>
* **Visma Dinero**
  * Replace any of the following with the proxy base URL:
    * `https://api.dinero.dk/v1/<organizationId>`
    * `https://api.dinero.dk/v1.2/<organizationId>`
  * API Documentation: <https://api.dinero.dk/openapi/index.html>
* **Exact Online**
  * Replace any of the following with the proxy base URL:
    * `https://start.exactonline.nl/api/v1/<division>`
    * `https://start.exactonline.nl/api/v1/beta/<division>`
    * `https://start.exactonline.nl` (for endpoints without division)
  * API Documentation: <https://start.exactonline.nl/docs/HlpRestAPIResources.aspx?SourceAction=10>
* **QuickBooks Online**
  * Replace: `https://quickbooks.api.intuit.com/v3/company/<realmId>` with the proxy base URL
  * API Documentation: <https://developer.intuit.com/app/developer/qbo/docs/api/accounting/all-entities/account>
* **Xero**
  * Replace: `https://api.xero.com/api.xro/2.0` with the proxy base URL
  * API Documentation: <https://developer.xero.com/documentation/api/accounting/overview>
* **Bokio**
  * Replace: `https://api.bokio.se/v1/companies/<companyId>` with the proxy base URL
  * API Documentation: <https://docs.bokio.se/reference/overview>
* **Kleer**
  * Kleer Proxy.1 supports `GET`, `POST`, `PUT`, and `DELETE`.
  * Use relative Kleer company resource paths such as `client/invoice` or `supplier/invoice/{invoiceId}`. Omit the Kleer host, `/v1/`, and the `company/{companyId}/` prefix; Zwapgrid supplies the token and company ID from the consent.
  * To request JSON, set `Content-Type: application/json` even for `GET`. For XML, use `application/xml`. Use the exact value without charset parameters; `Accept` does not select the response format.
  * API Documentation: [Kleer API documentation](https://api-doc.kleer.se/)
* **DATEV Online**
  * Replace the DATEV Accounting Data Exchange base URL for your environment (`https://accounting-data-exchange.api.datev.de/platform/v1` or `https://accounting-data-exchange.api.datev.de/platform-sandbox/v1`) with the proxy base URL.
  * Use relative paths beginning with `clients/{selectedCompanyId}/`, such as `clients/{selectedCompanyId}/fiscal-years`. The connection fixes the environment and selected company; another company or DATEV product cannot be targeted.
  * Proxy.1 accepts `GET`, `POST`, `PUT`, `PATCH`, and `DELETE` within that boundary, subject to DATEV's route and method rules. An account-postings `POST` starts an export job; it does not post accounting entries.
  * Request and successful-response bodies are limited to 16 MiB. Oversized responses fail rather than returning partial data; check provider pagination metadata against each export response.
  * API Documentation: [DATEV Accounting Data Exchange](https://developer.datev.de/en/product-detail/accounting-dataexchange/1/reference)
  * Setup: [DATEV Online setup guide](/client-portal/systems/setup-guides/datev.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zwapgrid.com/proxy.1/proxy.1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.