Elements Integration Changes
With version 1.1, we have introduced a simpler and more secure way of integrating HAPI Elements. It is explained in Including the HAPI Elements Script section of Setting Up page, and we are deprecating the unsecure and not so simple ways of integrating HAPI Elements.
ATS Partners have time to migrate to the new way of integrating HAPI Elements and when the deadline is reached, the deprecated ways will be disabled. The removal/deadline date is: 31st of December 2023.
The reason the below methods are deprecated is, the fact that sensitive credentials such as clientToken needed to be in the URL when loading the loader.js script and in many parts of application pipeline, the URLs may be logged like on monitoring tools such as New Relic, Datadog, Apache or Nginx logs etc.
Removal of the need to pass partnerId and clientId
Prior to version 1.1, the ATS, at the time of loading HAPI Elements script, needed to pass partnerId and clientId, this is no longer required and simply passing clientToken is enough to integrate with HAPI Elements.
[RECOMMENDED] Secure and simpler way of integration
Please refer to Including the HAPI Elements Script.
Deprecated integration methods with GET
The two methods below of including loader.js via GET request (or <script src=""> which also does a GET request) has a risk of leaking the sensitive information.