You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Change to new endpoints
Make use of the actual implementation (v1.6)
Backward compatibility:
The updated SDK must be fully backward compatible to enable smooth migration for existing integrations without significant conversion efforts. Existing functionalities should be retained in full and unchanged.
Flexible response configuration via query parameters:
The new API allows targeted control of the identifiers contained in the response via a query parameter. In addition to the previous TPID identifier, the SYNC_ID and/or ETPID can also be requested via the new interfaces. This configuration option must be designed to be flexible and easily accessible for SDK users. If necessary, this could be done simply as a new optional parameter in the fetchPermission function, for example.
Preconfigured default values:
By default, only the TPID should be queried in the SDK. An extension to include the additional identifiers (SYNC_ID, ETPID) can be configured by the developer in the SDK if required. The previous default case should be backward compatible.