Welcome, developer!
We’re happy you’re here! On this site you will find all the resources you need to create great integrations with Tripletex, whether you’re just starting out or working on an existing integration. On this page we will keep you updated on the latest news regarding the Tripletex API, and we have also gathered all our documentation, FAQs, how-to guides and code examples in one place. If you have any feedback please let us know.
Latest news
-
Upcoming changes to discount inheritance
Hello Developers! Currently, no discount is automatically populated when creating orders or orderlines via API. This has to be defined per object/subelement. In the next month, we plan to introduce discount inheritance from customers and products to orders and orderlines. E.g. if customer.discountPercentage has a value set, then any orders you create with this customer……
-
New outbound IP ranges
Hello Developers! Two months from now, on 20.11.2025, we will be changing our outbound IP addresses. This is only relevant if we connect to you – for example via webhook delivery – and you have whitelisted us. It does not impact your connection to us in any way. Here is our upcoming IPv4 ranges for……
-
OpenAPI Migration Update: Released!
Hello Developers, We’re pleased to announce that our transition from Swagger to OpenAPI is officially released.
-
Upcoming Migration to OpenAPI: What You Need to Know
We are transitioning from Swagger to OpenAPI for our API documentation. The JSON file will change from swagger.json to openapi.json. The old swagger.json will soon be frozen. We encourage all developers to transition to openapi.json as soon as it is released for the API’s latest updates. Details on the release will follow shortly.
-
Exciting Update: Welcome to Our New API Test Environment!
We’re thrilled to announce the launch of our brand-new API test environment. Starting today, you can register a new account and access the new test environment at api-test.tripletex.tech.
-
Important Update: Session Token Expiry Date [Updated]
This change has for now been reverted, and the previous functionality is currently restored. While this update is not in effect right now, it will be re-implemented in the near future. However, at this time, we do not have a specific release date.
