Practical DATEV Integration with Klardaten's API

DATEVconnect is the technical basis for many DATEV integrations, but operating it in practice can be more involved than expected. Rate limits, local installation requirements, missing internet accessibility, and different DATEV environments all affect production use. Klardaten provides an API layer that lets applications retrieve DATEV data in a controlled and automated way.

What’s DATEVconnect?

DATEVconnect is an interface for exchanging data between DATEV programs and external applications. It is commonly used in accounting, payroll, and document management scenarios. In practice, however, it depends on local infrastructure: DATEVconnect is not available over the internet by default, and rate limits or installation details can make integration harder. Klardaten adds an API layer that makes DATEVconnect easier to use from connected systems.

Simple Setup with Klardaten API Connector

Connecting DATEV through the Klardaten API mainly involves three steps:

1. Register Your User: Sign up on the Klardaten platform by creating your user account.
2. Register a DATEV Client Instance: Once your account is registered, you’ll create a DATEV client instance by providing your Beraternummer (advisor number). This step connects the DATEV system to our platform.
3. Install the API Connector: Install the Klardaten API connector on the Windows machine where DATEVconnect is available. The installation is supported by a setup wizard.

Should you run into any issues during setup, our support team is always available to assist you.

Example Use Cases with API Requests

Let’s look at how you can use our API in practice.

Access Token and Instance ID Requirements

Before executing the examples below, you must obtain an access token by registering or logging in. You will use this token to authenticate the API requests. Additionally, upon creating a client instance, you will receive an instance_id in the response, which must be included in the request header x-client-instance-id for further API communication.

Register User

The response will include an access token.

Create Instance

Example JSON response:

Now that you have both the access token and the client instance ID, you can proceed with the examples below to interact with the Klardaten API. Ensure that your Authorization header contains the access token and the x-client-instance-id header includes the instance ID for all requests.

Below are two common API requests for interacting with DATEV data.

Example 1: Retrieve Client Data

Here’s a simple curl request to retrieve a list of clients from DATEVconnect:

This request pulls client data, which you can use to automate accounting or client management workflows. Here, you find the content of a single entry in the JSON response:

Example 2: Retrieve Documents

Do you need to retrieve documents from DATEV? Here’s how you can do that with our API and DATEVconnect:

Here’s an example of the content of the JSON response for a single document:

These examples show how client and document data can be retrieved through the API. Based on that access, teams can build internal applications, reporting workflows, or recurring automation steps.

Support and Documentation

For DATEV integrations, the API is only one part of the implementation. The connector must run where DATEVconnect is available, and the connection needs to remain understandable in day-to-day operation. Klardaten supports both the initial setup and questions that come up during operation.

Documentation covers installation, API usage, and troubleshooting. It describes the necessary steps, headers, credentials, and common checks so the integration can be set up reproducibly.

Why Use Klardaten’s API?

The Klardaten API addresses several common obstacles in production DATEVconnect setups:

• Optimized Rate Limits: The API is designed to process recurring requests more predictably without putting unnecessary load on DATEV systems.

• Predictable Response Times: Data retrieval should be reliable and transparent for connected applications.

• Secure Internet-Based Access: DATEVconnect is not available over the internet by default. Klardaten provides a controlled connection layer for access to approved DATEV data.

• Less Integration Overhead: Teams do not have to operate the complete DATEVconnect integration layer themselves and can focus more on the actual use case.

Ready to Get Started?

If you want to use DATEV data in your own applications, reporting, or automation workflows, the Klardaten API can simplify the technical connection. The key questions are which DATEV data is needed, where DATEVconnect runs, and which processes should build on top of it.

Contact us if you want to review a concrete DATEVconnect use case.