22.04.2026 14:55:00

Changes in the OTE Web Services User Manual

 

In connection with the update of the OTE Web Services User Manual, we are publishing, for informational purposes, an overview of the main changes introduced by the new version.

The document reflects changes in the technical implementation of the services as well as new access URLs.
This overview is for informational purposes only and is intended to make it easier to navigate the differences between the previous and the current version of the documentation.

 

DESCRIPTION OF CHANGE EFFECTIVE / STATUS
New Service Addresses
Original service addresses:
Effective from: 28 April 2026
Changes in Response Examples for Individual Services
 
In the new version of the access endpoints, the sample SOAP responses have been modified.

The original sample format, for example:
<SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
                   xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
  <SOAP-ENV:Body>
 
has been replaced in the new version by the following format:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
Effective from: 28 April 2026
What Remains Unchanged
According to the current manual, the interface remains based on SOAP 1.1 / 1.2, WSDL, and XML schemas.
The new version of the manual also states compatibility with the existing web service interface.
From an integration perspective, this is therefore not a change to the interface type, but primarily a change in the technical implementation and service addressing.
Effective from: 22 April 2026

 

Required Actions on Your Side

Please update the configuration of your client application to use the new service URL and the new WSDL.
We also recommend verifying HTTPS access and, if applicable, checking the related firewall, proxy, or security rule configuration for the new service address.

The URL change follows directly from the new version of the manual, which also describes the new technical implementation of the services.

For an unspecified transition period, both URLs will be operated in parallel. However, to ensure long-term stability and compatibility, we strongly recommend updating the configured endpoints in all automation tools. 

The definitive change date will be communicated with sufficient advance notice.