PTV xServer API Version 1 – end of support in June 2026 - migrate now

[Bernd Welter]

Here's some important infor for xServer API V1 users you can't afford to miss!

The next generation of PTV developer solutions is designed to bring you unparalleled performance, security, and functionality:

PTV Developer
• Launched in 2021, this powerful cloud-based service offers cutting-edge features that will elevate your business operations.

Why Migrate?

• Enhanced Optimization: Utilize the most powerful optimization engine with PTV Developer Route Optimization OptiFlow API.
• Faster Maps: Experience accelerated application performance with new vector technology.
• Versatile Map Providers: Access OpenStreetMap as a secondary map provider.
• Accurate Emission Calculations: Comply with the latest standards like ISO14083 and the GLEC framework for precise CO2 calculations.
• Advanced Features: Enjoy new places and single field search, extended Map Matching, detailed toll calculations, Multi Travel-Time Matrices, and much more.

Support and Security:

• End of Support for PTV xServer API Version 1: Effective June 30th, 2026, this version will no longer receive updates or bug fixes. This includes crucial security updates, making it vulnerable to risks if continued in use.
• Recommendation: We strongly recommend migrating to PTV Developer to ensure your systems remain secure and up-to-date.

We’re here to Help! Our dedicated Customer Success Team is committed to making your transition seamless and efficient. We offer:

• Technical Consulting: Evaluate your current setup and receive hands-on assistance tailored to your needs.
• Personalized Support: Schedule an individual appointment with your PTV Logistics contact to ensure all requirements for a successful migration are addressed.

Reach out now to experience the full potential of PTV’s latest innovations.

Please find more information, FAQs and contact options to our specialists here:

[Bernd Welter]

Sidenote:
I still get requests from long term xServer1 users that they want to start implementing topics such as

• Toll calculation
• Emission based on latest standards

with xServer 1.

This doesn't work!

We do not implement or maintain such topics in the more than 20 year old interfaces as we cannot afford to spend implementation efforts in three different API versions. This is simply inefficient.
Please consider to migrate to Developer (or xServer2 if you are onPremise!)

Some more detailed answer:

• TOLL: more and more current toll systems make use of vehicle properties defined solely for the purpose of the toll, e.g. the CO2EmissionClassEU. We will not invent these new properties in the old API. THerefore the toll in xROute1 (based on basic toll btw) cannot cover all the latest requirements of the current toll standards.
• EmissionCalculation: this is even more complicated as providing access to a whole new emission standard such as ISO 14083 invent way more than just a single property.