Brief Description
Some of our data is provided via APIs (Application Programming Interfaces): List of our APIs.
This page describes all the important points for accessing our APIs.
Technical Description
Tools for Access
Access is only possible via HTTPS. All tools that support HTTPS can therefore be used (e.g. Postman, Bruno, curl, wget) or programming languages and libraries (Python requests, Java, JavaScript and many more).
URLs of the APIs
The URLs for access are contained in the data catalogue (list of our APIs) and in the respective cookbook pages.
API-Keys
To call the API, an API key must be resolved and included in the request header.
Obtaining New API Keys in the API Manager
Since 3 March 2025, keys can be obtained via our new API Manager.
Figure 1: Start page of the API Manager.
The most important steps:
- Registration with your e-mail address, surname, first name and password is required.
- One or more applications can then be created.
- In the API Manager overview page, an API can now be selected (“read more”, then “access with this plan”) and added to an app (“Select an App”)
Only one key can be obtained per API.
Use of the Keys in the Request Header
When the API is called, an “Authorisation” field with the key must be included in the HTTPS request header:
"Authorization": "Bearer .... add your key here ...."Other important points to note
Set User-Agent in Header
As a rule, a “User-Agent” field must also be included in the header.
"User-Agent": "... any value ...."Allow Redirects
Some of our APIs use redirects to other URLs. The corresponding options should therefore be set in the respective tool (e.g. allow_redirect=True or similar).
Activate Compression
If possible, the client should always use data compression. The client should list the formats it can handle, for example zip, Brotli and Deflate with one entry:
"Accept-Encoding": "zip, br, deflate"Examples
bruno
Bild 2: adding headers in API client tool bruno.
curl
…
…